| <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Apache Dubbo – Registration Center Description</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/registry/</link><description>Recent content in Registration Center Description on Apache Dubbo</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/registry/index.xml" rel="self" type="application/rss+xml"/><item><title>Docs3-V2: Overview</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/registry/overview/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/registry/overview/</guid><description> |
| <p>The registration center is the core component of Dubbo service governance. Dubbo relies on the coordination of the registration center to realize service (address) discovery. Automatic service discovery is the basis for microservices to achieve dynamic scaling, load balancing, and traffic management. Dubbo&rsquo;s service discovery mechanism has experienced interface-level service discovery in the Dubbo2 era and application-level service discovery in the Dubbo3 era. For details, see [Service Discovery Mechanism](/en/docs3-v2/java-sdk/concepts-and-architecture/service -discovery/) analysis to understand the specific evolution process.</p> |
| <h2 id="basic-usage">Basic usage</h2> |
| <p>The Dubbo registry component must be specified when developing an application. The configuration is very simple, just specify the cluster address of the registry:</p> |
| <p>Taking Spring Boot development as an example, add a registry configuration item in application.yml</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span>dubbo |
| </span></span><span style="display:flex;"><span> registry |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: {protocol}://{cluster-address} |
| </span></span></code></pre></div><p>Among them, protocol is the selected configuration center type, and cluster-address is the cluster address for accessing the registration center, such as</p> |
| <p><code>address: nacos://localshot:8848</code></p> |
| <p>If you need a cluster format address, you can use the backup parameter</p> |
| <p><code>address: nacos://localshot:8848?backup=localshot:8846,localshot:8847</code></p> |
| <blockquote> |
| <p>The application must specify the Dubbo registration center, even if the registration center is not enabled (you can set the address to be empty address=&lsquo;N/A&rsquo; ).</p> |
| </blockquote> |
| <p>In addition to the rest, depending on each configuration center, you can refer to the <a href="https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/config/properties/#registry">registry configuration reference manual</a> or expand through the parameters parameter.</p> |
| <h2 id="configuration-center-and-metadata-center">Configuration Center and Metadata Center</h2> |
| <p>The configuration center and metadata center are the basic components to realize Dubbo&rsquo;s high-level service governance capabilities. Compared with the registration center, the configuration of these two components is usually optional.</p> |
| <p>In order to be compatible with configurations of 2.6 and older versions, Dubbo will use it as both a metadata center and a configuration center for some registry types (such as Zookeeper, Nacos, etc.).</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span>dubbo |
| </span></span><span style="display:flex;"><span> registry |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: nacos://localhost:8848 |
| </span></span></code></pre></div><p>Default behavior after frame resolution</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span>dubbo |
| </span></span><span style="display:flex;"><span> registry |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: nacos://localhost:8848 |
| </span></span><span style="display:flex;"><span> config-center |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: nacos://localhost:8848 |
| </span></span><span style="display:flex;"><span> metadata-report |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: nacos://localhost:8848 |
| </span></span></code></pre></div><p>The default behavior can be adjusted or controlled by the following two parameters</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span>dubbo |
| </span></span><span style="display:flex;"><span> registry |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: nacos://localhost:8848 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">use-as-config-center</span>: <span style="color:#cb4b16">false</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">use-as-metadata-report</span>: <span style="color:#cb4b16">false</span> |
| </span></span></code></pre></div><h2 id="registration-center-ecology">Registration Center Ecology</h2> |
| <p>The mainstream registry implementations currently supported by the Dubbo backbone include</p> |
| <ul> |
| <li>Zookeeper</li> |
| <li>Nacos</li> |
| <li>Redis</li> |
| </ul> |
| <p>It also supports service discovery of Kubernetes and Mesh systems.</p> |
| <p>In addition, <a href="https://github.com/apache/dubbo-spi-extensions">Dubbo extension ecology</a> also provides registry extension implementations such as Consul, Eureka, and Etcd. Also welcome to contribute more registry implementations to the Dubbo ecosystem through <a href="../../spi/">registry spi extension</a>.</p> |
| <p>Dubbo also supports [specifying multiple registries] (../multiple-registry/) in an application, and grouping services according to registries, which makes service group management or service migration easier.</p></description></item><item><title>Docs3-V2: Zookeeper</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/registry/zookeeper/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/registry/zookeeper/</guid><description> |
| <h2 id="1-precondition">1 precondition</h2> |
| <ul> |
| <li>Understand <a href="../../../quick-start/spring-boot/">Dubbo basic development steps</a></li> |
| <li>Install and start <a href="https://zookeeper.apache.org/">Zookeeper</a></li> |
| </ul> |
| <h2 id="2-instructions-for-use">2 Instructions for use</h2> |
| <p>Check out <a href="https://github.com/apache/dubbo-samples/tree/master/3-extensions/registry/dubbo-samples-zookeeper">full sample code</a> here</p> |
| <h3 id="21-add-maven-dependency">2.1 Add Maven dependency</h3> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;properties&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;dubbo.version&gt;</span>3.0.8<span style="color:#268bd2">&lt;/dubbo.version&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;/properties&gt;</span> |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;dependencies&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;dependency&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;groupId&gt;</span>org.apache.dubbo<span style="color:#268bd2">&lt;/groupId&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;artifactId&gt;</span>dubbo<span style="color:#268bd2">&lt;/artifactId&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;version&gt;</span>${dubbo.version}<span style="color:#268bd2">&lt;/version&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;/dependency&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#586e75">&lt;!-- This dependency helps to introduce Curator and Zookeeper dependencies that are necessary for Dubbo to work with zookeeper as transitive dependencies --&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;dependency&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;groupId&gt;</span>org.apache.dubbo<span style="color:#268bd2">&lt;/groupId&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;artifactId&gt;</span>dubbo-dependencies-zookeeper<span style="color:#268bd2">&lt;/artifactId&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;version&gt;</span>${dubbo.version}<span style="color:#268bd2">&lt;/version&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;type&gt;</span>pom<span style="color:#268bd2">&lt;/type&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;/dependency&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;/dependencies&gt;</span> |
| </span></span></code></pre></div><p><code>dubbo-dependencies-zookeeper</code> will automatically add Zookeeper-related client dependencies to the application, reducing the cost of using Zookeeper for users. If there is a version compatibility problem during use, users can also add it by themselves instead of using <code>dubbo-dependencies-zookeeper</code> Curator, Zookeeper Client and other dependencies.</p> |
| <p>Since Dubbo uses Curator as a programming client interacting with Zookeeper Server, special attention should be paid to the compatibility between Zookeeper Server and Dubbo version dependencies</p> |
| <table> |
| <thead> |
| <tr> |
| <th>Zookeeper Server Version</th> |
| <th>Dubbo Version</th> |
| <th>Dubbo Zookeeper Dependency Package</th> |
| <th>Description</th> |
| </tr> |
| </thead> |
| <tbody> |
| <tr> |
| <td>3.4.x and below</td> |
| <td>3.0.x and above</td> |
| <td>dubbo-dependencies-zookeeper</td> |
| <td>transitive dependencies Curator 4.x, Zookeeper 3.4.x</td> |
| </tr> |
| <tr> |
| <td>3.5.x and above</td> |
| <td>3.0.x and above</td> |
| <td>dubbo-dependencies-zookeeper-curator5</td> |
| <td>transitive dependencies Curator 5.x, Zookeeper 3.7.x</td> |
| </tr> |
| <tr> |
| <td>3.4.x and above</td> |
| <td>2.7.x and below</td> |
| <td>dubbo-dependencies-zookeeper</td> |
| <td>transitive dependencies Curator 4.x, Zookeeper 3.4.x</td> |
| </tr> |
| <tr> |
| <td>3.5.x and above</td> |
| <td>2.7.x and below</td> |
| <td>None</td> |
| <td>Need to add Curator, Zookeeper and other related client dependencies</td> |
| </tr> |
| </tbody> |
| </table> |
| <h3 id="22-configure-and-enable-zookeeper">2.2 Configure and enable Zookeeper</h3> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#586e75"># application.yml</span> |
| </span></span><span style="display:flex;"><span>dubbo |
| </span></span><span style="display:flex;"><span> registry |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: zookeeper://localhost:2181 |
| </span></span></code></pre></div><p>or</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-properties" data-lang="properties"><span style="display:flex;"><span><span style="color:#586e75"># dubbo.properties</span> |
| </span></span><span style="display:flex;"><span>dubbo.registry.address<span style="color:#719e07">=</span><span style="color:#2aa198">zookeeper://localhost:2181</span> |
| </span></span></code></pre></div><p>or</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> address=<span style="color:#2aa198">&#34;zookeeper://localhost:2181&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><p><code>address</code> is the only attribute that must be specified to enable the zookeeper registration center, and in a production environment, <code>address</code> is usually specified as the cluster address, such as</p> |
| <p><code>address=zookeeper://10.20.153.10:2181?backup=10.20.153.11:2181,10.20.153.12:2181</code></p> |
| <p>It is also possible to configure protocol and address separately, such as</p> |
| <p><code>&lt;dubbo:registry protocol=&quot;zookeeper&quot; address=&quot;10.20.153.10:2181,10.20.153.11:2181,10.20.153.12:2181&quot; /&gt;</code></p> |
| <h2 id="3-advanced-configuration">3 Advanced configuration</h2> |
| <h3 id="31-authentication-and-authorization">3.1 Authentication and Authorization</h3> |
| <p>If Zookeeper enables authentication, Dubbo supports passing in the identity by specifying username and password.</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#586e75"># application.yml</span> |
| </span></span><span style="display:flex;"><span>dubbo |
| </span></span><span style="display:flex;"><span> registry |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: zookeeper://localhost:2181 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">username</span>: hello |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">password</span>: <span style="color:#2aa198">1234</span> |
| </span></span></code></pre></div><p>You can also directly expand the parameters on the address <code>address=zookeeper://hello:1234@localhost:2181</code></p> |
| <h3 id="32-group-isolation">3.2 Group isolation</h3> |
| <p>By specifying the <code>group</code> attribute, the logical isolation of microservice addresses can be achieved within the same Zookeeper cluster. For example, multiple sets of development environments can be isolated in one cluster, and isolation can be achieved at the address discovery level.</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#586e75"># application.yml</span> |
| </span></span><span style="display:flex;"><span>dubbo |
| </span></span><span style="display:flex;"><span> registry |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: zookeeper://localhost:2181 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">group</span>: daily1 |
| </span></span></code></pre></div><h3 id="33-other-extended-configurations">3.3 Other extended configurations</h3> |
| <p>Configure connection and session expiration time</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#586e75"># application.yml</span> |
| </span></span><span style="display:flex;"><span>dubbo |
| </span></span><span style="display:flex;"><span> registry |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: zookeeper://localhost:2181 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">timeout</span>: <span style="color:#2aa198">30</span> * <span style="color:#2aa198">1000</span>* <span style="color:#586e75"># Connection timeout, default 30s</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">session</span>: <span style="color:#2aa198">60</span> * <span style="color:#2aa198">1000</span>* <span style="color:#586e75"># Session timeout, default 60s</span> |
| </span></span></code></pre></div><p>The Zookeeper registry also supports some other control parameters, for details, see <a href="../../config/properties#registry">Registry configuration item manual</a></p> |
| <h2 id="4-how-it-works">4 How it works</h2> |
| <h3 id="41-dubbo2-node-structure">4.1 Dubbo2 node structure</h3> |
| <p><img src="https://dubbo.apache.org/imgs/user/zookeeper.jpg" alt="/user-guide/images/zookeeper.jpg"></p> |
| <p>process:</p> |
| <ul> |
| <li>When the service provider starts: write its own URL address to the <code>/dubbo/com.foo.BarService/providers</code> directory.</li> |
| <li>When the service consumer starts: subscribe to the provider URL address under the <code>/dubbo/com.foo.BarService/providers</code> directory. And write your own URL address to <code>/dubbo/com.foo.BarService/consumers</code> directory</li> |
| <li>When monitoring center starts: subscribe to all provider and consumer URL addresses under <code>/dubbo/com.foo.BarService</code> directory.</li> |
| </ul> |
| <p>The following functions are supported:</p> |
| <ul> |
| <li>When the provider has abnormal downtime such as power failure, the registration center can automatically delete the provider information</li> |
| <li>When the registration center restarts, the registration data and subscription requests can be automatically restored</li> |
| <li>When the session expires, the registration data and subscription request can be automatically restored</li> |
| <li>When <code>&lt;dubbo:registry check=&quot;false&quot; /&gt;</code> is set, the failed registration and subscription requests will be recorded, and the background will retry periodically</li> |
| <li>You can set zookeeper login information through <code>&lt;dubbo:registry username=&quot;admin&quot; password=&quot;1234&quot; /&gt;</code></li> |
| <li>The root node of zookeeper can be set through <code>&lt;dubbo:registry group=&quot;dubbo&quot; /&gt;</code>, if not configured, the default root node will be used.</li> |
| <li>Support <code>*</code> wildcard <code>&lt;dubbo:reference group=&quot;*&quot; version=&quot;*&quot; /&gt;</code>, you can subscribe to all groups of services and providers of all versions</li> |
| </ul> |
| <h3 id="42-dubbo3-node-structure">4.2 Dubbo3 node structure</h3></description></item><item><title>Docs3-V2: Nacos</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/registry/nacos/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/registry/nacos/</guid><description> |
| <h2 id="1-precondition">1 precondition</h2> |
| <ul> |
| <li>Understand <a href="../../../quick-start/spring-boot/">Dubbo basic development steps</a></li> |
| <li>Install and start <a href="https://nacos.io/zh-cn/docs/quick-start.html">Nacos service</a></li> |
| </ul> |
| <blockquote> |
| <p>When Dubbo uses <code>3.0.0</code> and above, it needs to use Nacos <code>2.0.0</code> and above.</p> |
| </blockquote> |
| <h2 id="2-instructions-for-use">2 Instructions for use</h2> |
| <p>Check here <a href="https://github.com/apache/dubbo-samples/tree/master/3-extensions/registry/dubbo-samples-nacos/dubbo-samples-nacos-registry">full sample code</a></p> |
| <h3 id="21-add-dependencies">2.1 Add dependencies</h3> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dependencies&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;dependency&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;groupId&gt;</span>org.apache.dubbo<span style="color:#268bd2">&lt;/groupId&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;artifactId&gt;</span>dubbo<span style="color:#268bd2">&lt;/artifactId&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;version&gt;</span>3.0.9<span style="color:#268bd2">&lt;/version&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;/dependency&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;dependency&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;groupId&gt;</span>com.alibaba.nacos<span style="color:#268bd2">&lt;/groupId&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;artifactId&gt;</span>nacos-client<span style="color:#268bd2">&lt;/artifactId&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;version&gt;</span>2.1.0<span style="color:#268bd2">&lt;/version&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;/dependency&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#586e75">&lt;!-- Introduce Dubbo Nacos extension, or you can add Nacos dependency directly as shown above--&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#586e75">&lt;!-- |
| </span></span></span><span style="display:flex;"><span><span style="color:#586e75"> &lt;dependency&gt; |
| </span></span></span><span style="display:flex;"><span><span style="color:#586e75"> &lt;groupId&gt;org.apache.dubbo&lt;/groupId&gt; |
| </span></span></span><span style="display:flex;"><span><span style="color:#586e75"> &lt;artifactId&gt;dubbo-registry-nacos&lt;/artifactId&gt; |
| </span></span></span><span style="display:flex;"><span><span style="color:#586e75"> &lt;version&gt;3.0.9&lt;/version&gt; |
| </span></span></span><span style="display:flex;"><span><span style="color:#586e75"> &lt;/dependency&gt; |
| </span></span></span><span style="display:flex;"><span><span style="color:#586e75"> --&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;/dependencies&gt;</span> |
| </span></span></code></pre></div><p>Add Dubbo and Nacos dependencies</p> |
| <blockquote> |
| <p>Dubbo <code>3.0.0</code> and above require nacos-client <code>2.0.0</code> and above</p> |
| </blockquote> |
| <h3 id="22-configure-and-enable-nacos">2.2 Configure and enable Nacos</h3> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#586e75"># application.yml (Spring Boot)</span> |
| </span></span><span style="display:flex;"><span>dubbo |
| </span></span><span style="display:flex;"><span> registry |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: nacos://localhost:8848 |
| </span></span></code></pre></div><p>or</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-properties" data-lang="properties"><span style="display:flex;"><span><span style="color:#586e75"># dubbo.properties</span> |
| </span></span><span style="display:flex;"><span>dubbo.registry.address<span style="color:#719e07">=</span><span style="color:#2aa198">nacos://localhost:8848</span> |
| </span></span></code></pre></div><p>or</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> address=<span style="color:#2aa198">&#34;nacos://localhost:8848&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><p>To enable the app, see what it looks like after registration or how it works, see [How it works](#4-How it works).</p> |
| <h2 id="3-advanced-configuration">3 Advanced configuration</h2> |
| <h3 id="31-authentication">3.1 Authentication</h3> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#586e75"># application.yml (Spring Boot)</span> |
| </span></span><span style="display:flex;"><span>dubbo |
| </span></span><span style="display:flex;"><span> registry |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: nacos://localhost:8848?username=nacos&amp;password=nacos |
| </span></span></code></pre></div><p>or</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-properties" data-lang="properties"><span style="display:flex;"><span><span style="color:#586e75"># dubbo.properties</span> |
| </span></span><span style="display:flex;"><span>dubbo.registry.address<span style="color:#719e07">:</span> <span style="color:#2aa198">nacos://nacos:nacos@localhost:8848</span> |
| </span></span></code></pre></div><h3 id="32-custom-namespace">3.2 Custom namespace</h3> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#586e75"># application.yml (Spring Boot)</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">dubbo</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">registry</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: nacos://localhost:8848?namespace=5cbb70a5-xxx-xxx-xxx-d43479ae0932 |
| </span></span></code></pre></div><p>or</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#586e75"># application.yml (Spring Boot)</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">dubbo</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">registry</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: nacos://localhost:8848 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">parameters.namespace</span>: 5cbb70a5-xxx-xxx-xxx-d43479ae0932 |
| </span></span></code></pre></div><h3 id="33-custom-grouping">3.3 Custom grouping</h3> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#586e75"># application.yml</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">dubbo</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">registry</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: nacos://localhost:8848 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">group</span>: dubbo |
| </span></span></code></pre></div><blockquote> |
| <p>If not configured, the group is specified by Nacos by default. Group and namespace represent different isolation levels in Nacos. Generally speaking, namespace is used to isolate different users or environments, and group is used to further group data in the same environment.</p> |
| </blockquote> |
| <h3 id="34-register-interface-level-consumers">3.4 Register interface-level consumers</h3> |
| <p>After Dubbo3.0.0, the parameter of whether to register consumers is added. If you need to register consumers to the nacos registration center, you need to set the parameter (register-consumer-url) to true, and the default is false.</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#586e75"># application.yml</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">dubbo</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">registry</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: nacos://localhost:8848?register-consumer-url=true |
| </span></span></code></pre></div><p>or</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#586e75"># application.yml</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">dubbo</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">registry</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: nacos://localhost:8848 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">parameters.register-consumer-url</span>: <span style="color:#cb4b16">true</span> |
| </span></span><span style="display:flex;"><span> |
| </span></span></code></pre></div><h3 id="35-more-configurations">3.5 More configurations</h3> |
| <table> |
| <thead> |
| <tr> |
| <th>Parameter name</th> |
| <th>Chinese description</th> |
| <th>Default value</th> |
| </tr> |
| </thead> |
| <tbody> |
| <tr> |
| <td>username</td> |
| <td>username to connect to Nacos Server</td> |
| <td>nacos</td> |
| </tr> |
| <tr> |
| <td>paasword</td> |
| <td>password to connect to Nacos Server</td> |
| <td>nacos</td> |
| </tr> |
| <tr> |
| <td>backup</td> |
| <td>backup address</td> |
| <td>null</td> |
| </tr> |
| <tr> |
| <td>namespace</td> |
| <td>Namespace ID</td> |
| <td>public</td> |
| </tr> |
| <tr> |
| <td>group</td> |
| <td>group name</td> |
| <td>DEFAULT_GROUP</td> |
| </tr> |
| <tr> |
| <td>register-consumer-url</td> |
| <td>Whether to register the consumer side</td> |
| <td>false</td> |
| </tr> |
| <tr> |
| <td>com.alibaba.nacos.naming.log.filename</td> |
| <td>initialization log file name</td> |
| <td>naming.log</td> |
| </tr> |
| <tr> |
| <td>endpoint</td> |
| <td>Connect to the connection point specified by Nacos Server, please refer to <a href="https://nacos.io/zh-cn/blog/address-server.html">documentation</a></td> |
| <td>empty</td> |
| </tr> |
| <tr> |
| <td>endpointPort</td> |
| <td>Connect to the connection point port specified by Nacos Server, you can refer to <a href="https://nacos.io/zh-cn/blog/address-server.html">documentation</a></td> |
| <td>empty</td> |
| </tr> |
| <tr> |
| <td>endpointQueryParams</td> |
| <td>endpoint query parameter query</td> |
| <td>null</td> |
| </tr> |
| <tr> |
| <td>isUseCloudNamespaceParsing</td> |
| <td>whether to parse namespace parameters in the cloud environment</td> |
| <td>true</td> |
| </tr> |
| <tr> |
| <td>isUseEndpointParsingRule</td> |
| <td>whether to enable endpoint parameter rule parsing</td> |
| <td>true</td> |
| </tr> |
| <tr> |
| <td>namingLoadCacheAtStart</td> |
| <td>whether to read the local cache first at startup</td> |
| <td>true</td> |
| </tr> |
| <tr> |
| <td>namingCacheRegistryDir</td> |
| <td>Specify the cache subdirectory, the location is &hellip;/nacos/{SUB_DIR}/naming</td> |
| <td>empty</td> |
| </tr> |
| <tr> |
| <td>namingClientBeatThreadCount</td> |
| <td>client heartbeat thread pool size</td> |
| <td>half of the number of CPUs of the machine</td> |
| </tr> |
| <tr> |
| <td>namingPollingThreadCount</td> |
| <td>Client timing polling thread pool size for data update</td> |
| <td>half of the CPU number of the machine</td> |
| </tr> |
| <tr> |
| <td>namingRequestDomainMaxRetryCount</td> |
| <td>Number of retries requested by client to Nacos Server via HTTP</td> |
| <td>3</td> |
| </tr> |
| <tr> |
| <td>namingPushEmptyProtection</td> |
| <td>When the service does not have a valid (healthy) instance, whether to enable the protection, after enabling it, the old service instance will be used</td> |
| <td>false</td> |
| </tr> |
| <tr> |
| <td>push.receiver.udp.port</td> |
| <td>port of client UDP</td> |
| <td>null</td> |
| </tr> |
| </tbody> |
| </table> |
| <p>After the nacos-server@<code>1.0.0</code> version, the client is supported to control some behaviors of the instance by reporting some instances containing specific metadata to the server.</p> |
| <table> |
| <thead> |
| <tr> |
| <th>Parameter name</th> |
| <th>Chinese description</th> |
| <th>Default value</th> |
| </tr> |
| </thead> |
| <tbody> |
| <tr> |
| <td>preserved.heart.beat.timeout</td> |
| <td>The time (in milliseconds) from healthy to unhealthy after the instance does not send a heartbeat</td> |
| <td>15000</td> |
| </tr> |
| <tr> |
| <td>preserved.ip.delete.timeout</td> |
| <td>The instance is deleted by the server after the instance does not send a heartbeat (milliseconds)</td> |
| <td>30000</td> |
| </tr> |
| <tr> |
| <td>preserved.heart.beat.interval</td> |
| <td>Interval time for the instance to report the heartbeat on the client (milliseconds)</td> |
| <td>5000</td> |
| </tr> |
| <tr> |
| <td>preserved.instance.id.generator</td> |
| <td>The id generation strategy of this instance, when the value is <code>snowflake</code>, it will increase from 0</td> |
| <td>simple</td> |
| </tr> |
| <tr> |
| <td>preserved.register.source</td> |
| <td>Registration instance registration service framework type (such as Dubbo, Spring Cloud, etc.)</td> |
| <td>empty</td> |
| </tr> |
| </tbody> |
| </table> |
| <p>These parameters can be configured to Nacos through parameter expansion in a manner similar to <code>namespace</code>, such as</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-properties" data-lang="properties"><span style="display:flex;"><span>dubbo.registry.parameters.preserved.heart.beat.timeout<span style="color:#719e07">=</span><span style="color:#2aa198">5000</span> |
| </span></span></code></pre></div><h2 id="4-how-it-works">4 How it works</h2> |
| <p>The following is just to show the working principle of Nacos as the Dubbo registration center. It is recommended to use <a href="https://github.com/apache/dubbo-admin">Dubbo Admin</a> for Dubbo service operation and maintenance</p> |
| <h3 id="41-dubbo2-registration-data">4.1 Dubbo2 registration data</h3> |
| <p>Then, restart your Dubbo application, and Dubbo&rsquo;s service provision and consumption information can be displayed in the Nacos console:</p> |
| <p><img src="https://dubbo.apache.org/imgs/blog/dubbo-registry-nacos-1.png" alt="dubbo-registry-nacos-1.png"></p> |
| <p>As shown in the figure, the service name prefixed with <code>providers:</code> is the meta information of the service provider, and <code>consumers:</code> represents the meta information of the service consumer. Click &ldquo;<strong>Details</strong>&rdquo; to view the service status details:</p> |
| <p><img src="https://dubbo.apache.org/imgs/blog/dubbo-registry-nacos-2.png" alt="image-dubbo-registry-nacos-2.png"></p> |
| <h3 id="42-dubbo3-registration-data">4.2 Dubbo3 registration data</h3> |
| <p>The &ldquo;service name&rdquo; for application-level service discovery is the application name</p> |
| <blockquote> |
| <p>Dubbo3 adopts the dual registration mode of &ldquo;application-level service discovery + interface-level service discovery&rdquo; by default, so you will find that application-level services (application names) and interface-level services (interface names) appear in the Nacos console at the same time, you can configure <code>dubbo .registry.register-mode=instance/interface/all</code> to change the registration behavior.</p> |
| </blockquote></description></item><item><title>Docs3-V2: Multicast</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/registry/multicast/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/registry/multicast/</guid><description> |
| <p>The Multicast registration center does not need to start any central nodes, as long as the broadcast address is the same, they can discover each other.</p> |
| <p><img src="https://dubbo.apache.org/imgs/user/multicast.jpg" alt="/user-guide/images/multicast.jpg"></p> |
| <h2 id="1-instructions-for-use">1 Instructions for use</h2> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> address=<span style="color:#2aa198">&#34;multicast://224.5.6.7:1234&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><p>or</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> protocol=<span style="color:#2aa198">&#34;multicast&#34;</span> address=<span style="color:#2aa198">&#34;224.5.6.7:1234&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><h4 id="notice">Notice:</h4> |
| <p>In order to reduce the amount of broadcasting, Dubbo uses unicast to send provider address information to consumers by default. |
| If multiple consumer processes are started on a machine at the same time, the consumer must declare <code>unicast=false</code>, otherwise only one consumer can receive the message; when the server and the consumer run on the same machine, the consumer It is also necessary to declare <code>unicast=false</code>, otherwise the consumer cannot receive the message, resulting in No provider available for the service exception:</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:application</span> name=<span style="color:#2aa198">&#34;demo-consumer&#34;</span><span style="color:#268bd2">&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;dubbo:parameter</span> key=<span style="color:#2aa198">&#34;unicast&#34;</span> value=<span style="color:#2aa198">&#34;false&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;/dubbo:application&gt;</span> |
| </span></span></code></pre></div><p>or</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:consumer&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;dubbo:parameter</span> key=<span style="color:#2aa198">&#34;unicast&#34;</span> value=<span style="color:#2aa198">&#34;false&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;/dubbo:consumer&gt;</span> |
| </span></span></code></pre></div><h2 id="2-how-it-works">2 How it works</h2> |
| <h3 id="21-basic-process">2.1 Basic process</h3> |
| <ol start="0"> |
| <li>The provider broadcasts its own address when it starts</li> |
| <li>Broadcast subscription request when consumer starts</li> |
| <li>When the provider receives the subscription request, it will unicast its own address to the subscribers. If <code>unicast=false</code> is set, it will broadcast to the subscribers</li> |
| <li>When the consumer receives the provider&rsquo;s address, it connects to the address to make an RPC call.</li> |
| </ol> |
| <h3 id="22-restrictions-on-use">2.2 Restrictions on Use</h3> |
| <p>Multicast is limited by the network structure and is only suitable for small-scale applications or development stages. Multicast address segment: 224.0.0.0 - 239.255.255.255</p></description></item><item><title>Docs3-V2: Redis</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/registry/redis/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/registry/redis/</guid><description> |
| <h2 id="precondition">precondition</h2> |
| <ul> |
| <li>Understand <a href="../../../quick-start/spring-boot/">Dubbo basic development steps</a></li> |
| <li>Install and start the <a href="http://redis.io">Redis</a> service</li> |
| </ul> |
| <h2 id="instructions-for-use">Instructions for use</h2> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> address=<span style="color:#2aa198">&#34;redis://10.20.153.10:6379&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><p>or</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> address=<span style="color:#2aa198">&#34;redis://10.20.153.10:6379?backup=10.20.153.11:6379,10.20.153.12:6379&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><p>or</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> protocol=<span style="color:#2aa198">&#34;redis&#34;</span> address=<span style="color:#2aa198">&#34;10.20.153.10:6379&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><p>or</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> protocol=<span style="color:#2aa198">&#34;redis&#34;</span> address=<span style="color:#2aa198">&#34;10.20.153.10:6379,10.20.153.11:6379,10.20.153.12:6379&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><h2 id="options">options</h2> |
| <ul> |
| <li>You can set the prefix of the key in redis through <code>&lt;dubbo:registry group=&quot;dubbo&quot; /&gt;</code>, the default is <code>dubbo</code>.</li> |
| <li>The redis cluster strategy can be set via <code>&lt;dubbo:registry cluster=&quot;replicate&quot; /&gt;</code>, the default is <code>failover</code>: |
| <ul> |
| <li><code>failover</code>: Only write and read any one, and retry another one when it fails, the server needs to configure data synchronization by itself</li> |
| <li><code>replicate</code>: Write to all servers at the same time on the client side, only read a single server, the server side does not need to be synchronized, the registration center cluster increases, and the performance pressure will also be greater</li> |
| </ul> |
| </li> |
| </ul> |
| <h2 id="working-principle">working principle</h2> |
| <p>A registry implemented based on Redis [^1].</p> |
| <p>Redis expired data detects dirty data through heartbeat, the server time must be synchronized, and there is a certain pressure on the server, otherwise the expiration detection will be inaccurate</p> |
| <p><img src="https://dubbo.apache.org/imgs/user/dubbo-redis-registry.jpg" alt="/user-guide/images/dubbo-redis-registry.jpg"></p> |
| <p>Use Redis&rsquo;s Key/Map structure to store data structures:</p> |
| <ul> |
| <li>The main key is the service name and type</li> |
| <li>The Key in the Map is the URL address</li> |
| <li>The Value in the Map is the expiration time, which is used to judge dirty data, and the dirty data will be deleted by the monitoring center [^3]</li> |
| </ul> |
| <p>Use Redis&rsquo;s Publish/Subscribe events to notify data changes:</p> |
| <ul> |
| <li>Differentiate the event type by the value of the event: <code>register</code>, <code>unregister</code>, <code>subscribe</code>, <code>unsubscribe</code></li> |
| <li>Ordinary consumers directly subscribe to the Key of the specified service provider, and will only receive <code>register</code>, <code>unregister</code> events of the specified service</li> |
| <li>The monitoring center subscribes to <code>/dubbo/*</code> through the <code>psubscribe</code> function, and will receive all change events of all services</li> |
| </ul> |
| <p>Call process:</p> |
| <ol start="0"> |
| <li>When the service provider starts, add the address of the current provider to <code>Key:/dubbo/com.foo.BarService/providers</code></li> |
| <li>And send <code>register</code> event to <code>Channel:/dubbo/com.foo.BarService/providers</code></li> |
| <li>When the service consumer starts, subscribe to <code>register</code> and <code>unregister</code> events from <code>Channel:/dubbo/com.foo.BarService/providers</code></li> |
| <li>Add the address of the current consumer to <code>Key:/dubbo/com.foo.BarService/consumers</code></li> |
| <li>After receiving the <code>register</code> and <code>unregister</code> events, the service consumer obtains the provider address list from <code>Key:/dubbo/com.foo.BarService/providers</code></li> |
| <li>When the service monitoring center starts, subscribe to <code>register</code> and <code>unregister</code>, and <code>subscribe</code> and <code>unsubscribe</code> events from <code>Channel:/dubbo/*</code></li> |
| <li>After receiving the <code>register</code> and <code>unregister</code> events, the service monitoring center obtains the provider address list from <code>Key:/dubbo/com.foo.BarService/providers</code></li> |
| <li>After receiving the <code>subscribe</code> and <code>unsubscribe</code> events, the service monitoring center obtains the consumer address list from <code>Key:/dubbo/com.foo.BarService/consumers</code></li> |
| </ol></description></item><item><title>Docs3-V2: Multiple Registries</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/registry/multiple-registry/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/registry/multiple-registry/</guid><description> |
| <h2 id="1-associated-service-and-multiple-registration-centers">1 Associated service and multiple registration centers</h2> |
| <h3 id="11-global-default-registration-center">1.1 Global Default Registration Center</h3> |
| <p>The Dubbo registry and services are configured independently. Usually, developers do not need to set the relationship between services and registry components. The Dubbo framework will automatically perform the following actions:</p> |
| <ul> |
| <li>For all Service services, register the service address with all global default registries.</li> |
| <li>For all Reference services, subscribe service addresses from all global default registries.</li> |
| </ul> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yml" data-lang="yml"><span style="display:flex;"><span><span style="color:#586e75"># application.yml (Spring Boot)</span> |
| </span></span><span style="display:flex;"><span>dubbo |
| </span></span><span style="display:flex;"><span> registries |
| </span></span><span style="display:flex;"><span> beijing Registry |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: zookeeper://localhost:2181 |
| </span></span><span style="display:flex;"><span> shanghai Registry |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: zookeeper://localhost:2182 |
| </span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-java" data-lang="java"><span style="display:flex;"><span><span style="color:#268bd2">@DubboService</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">public</span> <span style="color:#268bd2">class</span> <span style="color:#268bd2">DemoServiceImpl</span> <span style="color:#268bd2">implements</span> DemoService <span style="color:#719e07">{}</span> |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">@DubboService</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">public</span> <span style="color:#268bd2">class</span> <span style="color:#268bd2">HelloServiceImpl</span> <span style="color:#268bd2">implements</span> HelloService <span style="color:#719e07">{}</span> |
| </span></span></code></pre></div><p>The above takes Spring Boot development as an example (XML and API methods are similar) to configure two global default registries, beijingRegistry and shanghaiRegistry, and the services DemoService and HelloService will be registered to the two default registries respectively.</p> |
| <p>In addition to the framework mentioned above to automatically set the global registry for the service, there are two ways to flexibly adjust the association between the service and multiple registry.</p> |
| <h3 id="12-set-the-global-default-registration-center">1.2 Set the global default registration center</h3> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yml" data-lang="yml"><span style="display:flex;"><span><span style="color:#586e75"># application.yml (Spring Boot)</span> |
| </span></span><span style="display:flex;"><span>dubbo |
| </span></span><span style="display:flex;"><span> registries |
| </span></span><span style="display:flex;"><span> beijing Registry |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: zookeeper://localhost:2181 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">default</span>: <span style="color:#cb4b16">true</span> |
| </span></span><span style="display:flex;"><span> shanghai Registry |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: zookeeper://localhost:2182 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">default</span>: <span style="color:#cb4b16">false</span> |
| </span></span></code></pre></div><p><code>default</code> is used to set the global default registry, the default value is <code>true</code> which is regarded as the global registry. Services that do not specify a registry id will automatically register or subscribe to the global default registry.</p> |
| <h3 id="13-display-associated-services-and-registry">1.3 Display associated services and registry</h3> |
| <p>By adding the registry configuration to the Dubbo service definition component, the service is associated with the registry.</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-java" data-lang="java"><span style="display:flex;"><span><span style="color:#268bd2">@DubboServiceregistry</span> <span style="color:#719e07">=</span> <span style="color:#719e07">{</span><span style="color:#2aa198">&#34;beijingRegistry&#34;</span><span style="color:#719e07">}</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">public</span> <span style="color:#268bd2">class</span> <span style="color:#268bd2">DemoServiceImpl</span> <span style="color:#268bd2">implements</span> DemoService <span style="color:#719e07">{}</span> |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">@DubboServiceregistry</span> <span style="color:#719e07">=</span> <span style="color:#719e07">{</span><span style="color:#2aa198">&#34;shanghaiRegistry&#34;</span><span style="color:#719e07">}</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">public</span> <span style="color:#268bd2">class</span> <span style="color:#268bd2">HelloServiceImpl</span> <span style="color:#268bd2">implements</span> HelloService <span style="color:#719e07">{}</span> |
| </span></span></code></pre></div><p>After adding the above configuration, DemoService will only be registered to beijingRegistry, and HelloService will be registered to shanghaiRegistry.</p> |
| <h2 id="2-multi-registry-subscription">2 Multi-registry subscription</h2> |
| <p>Since service subscription involves address aggregation and routing address selection, the logic will be more complicated. From the perspective of a single service subscription, if there is a multi-registry subscription, it can be divided into two scenarios according to whether the addresses between the registries are aggregated.</p> |
| <h3 id="21-multi-registry-addresses-are-not-aggregated">2.1 Multi-registry addresses are not aggregated</h3> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> id=<span style="color:#2aa198">&#34;hangzhouRegistry&#34;</span> address=<span style="color:#2aa198">&#34;10.20.141.150:9090&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> id=<span style="color:#2aa198">&#34;qingdaoRegistry&#34;</span> address=<span style="color:#2aa198">&#34;10.20.141.151:9010&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><p>For the independently configured registry component shown above, the address list is completely isolated on the consumer side by default, and the load balancing address selection needs to go through two steps:</p> |
| <ol> |
| <li>Site selection among the registration center clusters, select a cluster</li> |
| <li>Select the address in the registration center cluster, and perform address screening in the cluster</li> |
| </ol> |
| <p><img src="https://dubbo.apache.org/imgs/v3/registry/no-aggregation.png" alt="multi-registris-no-aggregation"></p> |
| <p>Below we will focus on how to control <strong>Registration center inter-cluster site selection</strong>, the optional strategies are as follows |
| <strong>random</strong> |
| Each request is randomly assigned to a registry cluster</p> |
| <blockquote> |
| <p>There will be an availability check in the random process, that is, each cluster must ensure that at least one address is available before it can be selected.</p> |
| </blockquote> |
| <p><strong>preferred priority</strong></p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> id=<span style="color:#2aa198">&#34;hangzhouRegistry&#34;</span> address=<span style="color:#2aa198">&#34;10.20.141.150:9090&#34;</span> preferred=<span style="color:#2aa198">&#34;true&#34;</span><span style="color:#268bd2">/&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> id=<span style="color:#2aa198">&#34;qingdaoRegistry&#34;</span> address=<span style="color:#2aa198">&#34;10.20.141.151:9010&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><p>If there is a registry cluster configured with <code>preferred=&quot;true&quot;</code>, all traffic will be routed to this cluster.</p> |
| <p><strong>weighted</strong></p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> id=<span style="color:#2aa198">&#34;hangzhouRegistry&#34;</span> address=<span style="color:#2aa198">&#34;10.20.141.150:9090&#34;</span> weight=<span style="color:#2aa198">&#34;100&#34;</span><span style="color:#268bd2">/&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> id=<span style="color:#2aa198">&#34;qingdaoRegistry&#34;</span> address=<span style="color:#2aa198">&#34;10.20.141.151:9010&#34;</span> weight=<span style="color:#2aa198">&#34;10&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><p>Based on weighted random load balancing, there will be about 10:1 traffic distribution among the above clusters.</p> |
| <p><strong>same zone priority</strong></p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> id=<span style="color:#2aa198">&#34;hangzhouRegistry&#34;</span> address=<span style="color:#2aa198">&#34;10.20.141.150:9090&#34;</span> zone=<span style="color:#2aa198">&#34;hangzhou&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> id=<span style="color:#2aa198">&#34;qingdaoRegistry&#34;</span> address=<span style="color:#2aa198">&#34;10.20.141.151:9010&#34;</span> zone=<span style="color:#2aa198">&#34;qingdao&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-java" data-lang="java"><span style="display:flex;"><span>RpcContext<span style="color:#719e07">.</span>getContext<span style="color:#719e07">().</span>setAttachment<span style="color:#719e07">(</span><span style="color:#2aa198">&#34;registry_zone&#34;</span><span style="color:#719e07">,</span> <span style="color:#2aa198">&#34;qingdao&#34;</span><span style="color:#719e07">);</span> |
| </span></span></code></pre></div><p>According to the traffic parameters carried in the Invocation or the parameters set through the context context on the current node, the traffic will be accurately guided to the corresponding cluster.</p> |
| <h3 id="22-multi-registry-address-aggregation">2.2 Multi-registry address aggregation</h3> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> address=<span style="color:#2aa198">&#34;multiple://127.0.0.1:2181?separator=;&amp;reference-registry=zookeeper://address11?backup=address12,address13;zookeeper://address21?backup=address22,address23&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><p>Here, a registration center starting with a special multiple protocol is added, where:</p> |
| <ul> |
| <li><code>multiple://127.0.0.1:2181</code> has no specific meaning, it is just a placeholder in a specific format, and the address can be specified at will</li> |
| <li><code>reference-registry</code> specifies the list of registry clusters to be aggregated. In the example, there are two clusters, <code>zookeeper://address11?backup=address12,address13</code> and <code>zookeeper://address21?backup=address22</code> ,address23<code>, which also specifies the cluster separator </code>separator=&quot;;&quot;`</li> |
| </ul> |
| <p>As shown in the figure below, the addresses of different registration center clusters will be aggregated into one address pool for load balancing or routing address selection on the consumer side.</p> |
| <p><img src="https://dubbo.apache.org/imgs/v3/registry/aggregation.png" alt="multi-registris-aggregation"></p> |
| <p>In version 3.1.0 and later, it is also supported to set specific attachments attributes on each registry cluster to achieve specific marking of addresses under the registry cluster, and then cooperate with Router component extensions such as TagRouter to realize cross-machine rooms traffic management capabilities.</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> address=<span style="color:#2aa198">&#34;multiple://127.0.0.1:2181?separator=;&amp;reference-registry=zookeeper://address11?attachments=zone=hangzhou,tag=middleware;zookeeper://address21&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><p>After adding <code>attachments=zone=hangzhou,tag=middleware</code>, all URL addresses from the registration center will automatically carry the two identifiers of <code>zone</code> and <code>tag</code>, which facilitates more flexible traffic management on the consumer side.</p> |
| <h2 id="3-scenario-example">3 Scenario example</h2> |
| <h3 id="31-scenario-1-cross-region-registration-service">3.1 Scenario 1: Cross-region registration service</h3> |
| <p>For example: Some services of the Chinese website are too late to be deployed in Qingdao, and are only deployed in Hangzhou, while other applications in Qingdao need to reference this service, so the service can be registered to two registration centers at the same time.</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> id=<span style="color:#2aa198">&#34;hangzhouRegistry&#34;</span> address=<span style="color:#2aa198">&#34;10.20.141.150:9090&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> id=<span style="color:#2aa198">&#34;qingdaoRegistry&#34;</span> address=<span style="color:#2aa198">&#34;10.20.141.151:9010&#34;</span> default=<span style="color:#2aa198">&#34;false&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#586e75">&lt;!-- Register with multiple registries --&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:service</span> interface=<span style="color:#2aa198">&#34;com.alibaba.hello.api.HelloService&#34;</span> version=<span style="color:#2aa198">&#34;1.0.0&#34;</span> ref=<span style="color:#2aa198">&#34;helloService&#34;</span> registry=<span style="color:#2aa198">&#34;hangzhouRegistry,qingdaoRegistry&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><h3 id="32-scenario-2-isolation-based-on-business">3.2 Scenario 2: Isolation based on business</h3> |
| <p>Some CRM services are specially designed for international websites, and some services are specially designed for Chinese websites.</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#586e75">&lt;!-- Multi-registry configuration --&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> id=<span style="color:#2aa198">&#34;chinaRegistry&#34;</span> address=<span style="color:#2aa198">&#34;10.20.141.150:9090&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> id=<span style="color:#2aa198">&#34;intlRegistry&#34;</span> address=<span style="color:#2aa198">&#34;10.20.154.177:9010&#34;</span> default=<span style="color:#2aa198">&#34;false&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#586e75">&lt;!-- Register with the Chinese Station Registration Center --&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:service</span> interface=<span style="color:#2aa198">&#34;com.alibaba.hello.api.HelloService&#34;</span> version=<span style="color:#2aa198">&#34;1.0.0&#34;</span> ref=<span style="color:#2aa198">&#34;helloService&#34;</span> registry=<span style="color:#2aa198">&#34;chinaRegistry&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#586e75">&lt;!-- Register with the International Station Registration Center --&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:service</span> interface=<span style="color:#2aa198">&#34;com.alibaba.hello.api.DemoService&#34;</span> version=<span style="color:#2aa198">&#34;1.0.0&#34;</span> ref=<span style="color:#2aa198">&#34;demoService&#34;</span> registry=<span style="color:#2aa198">&#34;intlRegistry&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><h3 id="33-scenario-3-invoking-services-based-on-business">3.3 Scenario 3: Invoking services based on business</h3> |
| <p>CRM needs to call the PC2 service of the Chinese station and the international station at the same time. PC2 is deployed in both the Chinese station and the international station. The interface and version number are the same, but the connected database is different.</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#586e75">&lt;!-- Multi-registry configuration --&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> id=<span style="color:#2aa198">&#34;chinaRegistry&#34;</span> address=<span style="color:#2aa198">&#34;10.20.141.150:9090&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> id=<span style="color:#2aa198">&#34;intlRegistry&#34;</span> address=<span style="color:#2aa198">&#34;10.20.154.177:9010&#34;</span> default=<span style="color:#2aa198">&#34;false&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#586e75">&lt;!-- Quote Chinese station service --&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:reference</span> id=<span style="color:#2aa198">&#34;chinaHelloService&#34;</span> interface=<span style="color:#2aa198">&#34;com.alibaba.hello.api.HelloService&#34;</span> version=<span style="color:#2aa198">&#34;1.0.0&#34;</span> registry=<span style="color:#2aa198">&#34;chinaRegistry&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#586e75">&lt;!-- Reference international station service --&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:reference</span> id=<span style="color:#2aa198">&#34;intlHelloService&#34;</span> interface=<span style="color:#2aa198">&#34;com.alibaba.hello.api.HelloService&#34;</span> version=<span style="color:#2aa198">&#34;1.0.0&#34;</span> registry=<span style="color:#2aa198">&#34;intlRegistry&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><p>If only the test environment temporarily needs to connect to two different registration centers, use vertical symbols to separate multiple different registration center addresses:</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#586e75">&lt;!-- Multi-registry configuration, separated by a vertical sign means connecting to multiple different registries at the same time, and multiple cluster addresses of the same registrant are separated by commas --&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> address=<span style="color:#2aa198">&#34;10.20.141.150:9090|10.20.154.177:9010&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#586e75">&lt;!-- Reference service --&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:reference</span> id=<span style="color:#2aa198">&#34;helloService&#34;</span> interface=<span style="color:#2aa198">&#34;com.alibaba.hello.api.HelloService&#34;</span> version=<span style="color:#2aa198">&#34;1.0.0&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div></description></item><item><title>Docs3-V2: Simple Registry</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/registry/simple/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/registry/simple/</guid><description> |
| <div class="pageinfo pageinfo-primary"> |
| <p>This function has been removed in Dubbo 2.7, please select <a href="../">other registry</a> for migration.</p> |
| </div> |
| <p>The Simple registry itself is an ordinary Dubbo service, which can reduce third-party dependencies and make the overall communication method consistent.</p> |
| <h2 id="configuration">configuration</h2> |
| <p>Expose the Simple registry as a Dubbo service:</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#719e07">&lt;?xml version=&#34;1.0&#34; encoding=&#34;UTF-8&#34;?&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;beans</span> xmlns=<span style="color:#2aa198">&#34;http://www.springframework.org/schema/beans&#34;</span> |
| </span></span><span style="display:flex;"><span> xmlns:xsi=<span style="color:#2aa198">&#34;http://www.w3.org/2001/XMLSchema-instance&#34;</span> |
| </span></span><span style="display:flex;"><span> xmlns:dubbo=<span style="color:#2aa198">&#34;http://dubbo.apache.org/schema/dubbo&#34;</span> |
| </span></span><span style="display:flex;"><span> xsi:schemaLocation=<span style="color:#2aa198">&#34;http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-4.3.xsd http://dubbo.apache.org/schema /dubbo http://dubbo.apache.org/schema/dubbo/dubbo.xsd&#34;</span><span style="color:#268bd2">&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#586e75">&lt;!-- Current application information configuration --&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;dubbo:application</span> name=<span style="color:#2aa198">&#34;simple-registry&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#586e75">&lt;!-- Expose service protocol configuration --&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;dubbo:protocol</span> port=<span style="color:#2aa198">&#34;9090&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#586e75">&lt;!-- Expose service configuration --&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;dubbo:service</span> interface=<span style="color:#2aa198">&#34;org.apache.dubbo.registry.RegistryService&#34;</span> ref=<span style="color:#2aa198">&#34;registryService&#34;</span> registry=<span style="color:#2aa198">&#34;N/A&#34;</span> ondisconnect=<span style="color:#2aa198">&#34;disconnect&#34;</span> callbacks=<span style="color:#2aa198">&#34;1000&#34;</span><span style="color:#268bd2">&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;dubbo:method</span> name=<span style="color:#2aa198">&#34;subscribe&#34;</span><span style="color:#268bd2">&gt;&lt;dubbo:argument</span> index=<span style="color:#2aa198">&#34;1&#34;</span> callback=<span style="color:#2aa198">&#34;true&#34;</span> <span style="color:#268bd2">/&gt;&lt;/dubbo:method&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;dubbo:method</span> name=<span style="color:#2aa198">&#34;unsubscribe&#34;</span><span style="color:#268bd2">&gt;&lt;dubbo:argument</span> index=<span style="color:#2aa198">&#34;1&#34;</span> callback=<span style="color:#2aa198">&#34;false&#34;</span> <span style="color:#268bd2">/&gt;&lt;/dubbo:method&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;/dubbo:service&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#586e75">&lt;!-- Implementation of a simple registration center, which can be expanded by itself to achieve cluster and state synchronization --&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;bean</span> id=<span style="color:#2aa198">&#34;registryService&#34;</span> class=<span style="color:#2aa198">&#34;org.apache.dubbo.registry.simple.SimpleRegistryService&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;/beans&gt;</span> |
| </span></span></code></pre></div><p>Quoting the Simple Registry service:</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> address=<span style="color:#2aa198">&#34;127.0.0.1:9090&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><p>or:</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:service</span> interface=<span style="color:#2aa198">&#34;org.apache.dubbo.registry.RegistryService&#34;</span> group=<span style="color:#2aa198">&#34;simple&#34;</span> version=<span style="color:#2aa198">&#34;1.0.0&#34;</span> ... <span style="color:#268bd2">&gt;</span> |
| </span></span></code></pre></div><p>or:</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:registry</span> address=<span style="color:#2aa198">&#34;127.0.0.1:9090&#34;</span> group=<span style="color:#2aa198">&#34;simple&#34;</span> version=<span style="color:#2aa198">&#34;1.0.0&#34;</span> <span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><h2 id="applicability-notes">Applicability Notes</h2> |
| <p>This <code>SimpleRegistryService</code> is just a simple implementation and does not support clustering. It can be used as a reference for a custom registry, but it is not suitable for direct use in a production environment.</p></description></item></channel></rss> |
