Help Center>
Application Service Mesh>
Best Practices>
Service Governance for Dubbo-based Applications>
Service Discovery Model
Updated on 2023-07-03 GMT+08:00
Service Discovery Model
Problems in the existing Dubbo model (summarized from the Dubbo community version 2.7.4):
- In the microservice architecture, the Registry manages applications (services) instead of external service interfaces. However, the Dubbo Registry manages Dubbo service interfaces, contrary to the Spring Cloud or Cloud Native registration mode.
- A Dubbo application (service) allows N Dubbo service interfaces to be registered. The more interfaces, the heavier the load of the Registry.
The existing Dubbo service model searches for service instances based on the Dubbo interface.
The Dubbo Cloud Native service discovery model adds an app layer to search for instances.
Parent topic: Service Governance for Dubbo-based Applications
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
