Help Center/ Application Service Mesh/ Best Practices/ Service Governance for Dubbo-based Applications/ Service Discovery Model

Updated on 2022-07-27 GMT+08:00

View PDF

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

Previous topic: Introduction

Next topic: SDK Adaptation Mode

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.