forked from docs/doc-exports
Reviewed-by: Kovács, Zoltán <zkovacs@t-systems.com> Co-authored-by: Dong, Qiu Jian <qiujiandong1@huawei.com> Co-committed-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
17 lines
1.6 KiB
HTML
17 lines
1.6 KiB
HTML
<a name="asm_bestpractice_3008"></a><a name="asm_bestpractice_3008"></a>
|
|
|
|
<h1 class="topictitle1">Service Discovery Model</h1>
|
|
<div id="body1568970862475"><p id="asm_bestpractice_3008__p1990012073215">Problems in the existing Dubbo model (summarized from the Dubbo community version 2.7.4):</p>
|
|
<ul id="asm_bestpractice_3008__ul116499357325"><li id="asm_bestpractice_3008__li1064933543211">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.</li><li id="asm_bestpractice_3008__li9177125414336">A Dubbo application (service) allows N Dubbo service interfaces to be registered. The more interfaces, the heavier the load of the Registry.</li></ul>
|
|
<p id="asm_bestpractice_3008__p16244123463218">The existing Dubbo service model searches for service instances based on the Dubbo interface.</p>
|
|
<p id="asm_bestpractice_3008__p142014122418"><span><img class="eddx" id="asm_bestpractice_3008__image112041210415" src="en-us_image_0000001181759886.png"></span></p>
|
|
<p id="asm_bestpractice_3008__p126069483342">The Dubbo Cloud Native service discovery model adds an app layer to search for instances.</p>
|
|
<p id="asm_bestpractice_3008__p9673641144710"><span><img class="eddx" id="asm_bestpractice_3008__image767311418471" src="en-us_image_0000001227360319.png"></span></p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_bestpractice_3001.html">Service Governance for Dubbo-based Applications</a></div>
|
|
</div>
|
|
</div>
|
|
|