Disadvantages of dubbo under microservice architecture

1.
Dubbo only implements service governance, and other components need to be integrated to achieve corresponding functions, such as:
distributed configuration: you can use Taobao's diamond and Baidu's disconf to achieve distributed configuration management.
Service tracking: You can use the open source Hydra
batch tasks of Jingdong: you can use the open source Elastic-Job

of Dangdang and there are 17 sub-projects (may be added) under Spring Cloud, which cover all aspects of the microservice architecture, and service governance is only one of them One aspect


2. Dubbo's RPC to implement some pain points of inter-service calls
a. The interface between the service provider and the caller is too dependent: the caller has a strong dependency on the provider's abstract interface, and requires strict management of version dependencies before There will not be a series of problems such as the inconsistency between the server and the caller, which causes the application to fail to compile successfully;
b. The service is sensitive to the platform, and it is difficult to simply reuse: Usually, when we provide external services, we will provide them in the form of REST, which can Implement cross-platform features.
When we want to provide a REST interface in Dubbo, we have to implement a layer of proxy to convert the RPC interface into a REST interface for external publishing. So Dangdang has added REST support to dubbox (an open source extension based on Dubbo).