1, Dubbo just focus on the governance between the services, configuration center, distributed tracking and other such content needs their own integration
2, Dubbo core functions:
A, remote communication
b, cluster fault tolerance
C, automatic discovery
|
Dubbo |
Springcloud |
Service Registration Center |
Zookeeper |
Springcloud Netflix Eureka |
Service invocation Mode |
Rpc |
REST API |
Service Monitoring |
Dubbo-monitor |
Springboot Admin |
Circuit Breaker |
Not perfect |
Springcloud Netflix Hystrix |
Service Gateway |
No |
Springcloud Netflix Zuul |
Distributed configuration |
No |
Springcloud Config |
Service tracking |
No |
Springcloud Sleuth |
Message bus |
No |
Springcloud Bus |
Data flow |
No |
Springcloud Stream |
Bulk tasks |
No |
Springcloud Task |
... |
... |
... |
Dubbo's function is only part of the Springcloud system, Dubbo is the product of the SOA era, focus on service invocation, traffic distribution, traffic monitoring and fusing, Springcloud is the product of the era of microservices architecture, considering all aspects of micro-service governance.
In terms of service governance, Dubbo is better than Springcloud:
1. Support More protocols
2. Higher efficiency with RPC protocol
3. Powerful background management
4, on-line support gray-scale publishing, failover
Dubbo Springcloud Comparison