| <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Apache Dubbo – How to smoothly migrate to the new functions of Dubbo3</title><link>https://dubbo.apache.org/en/overview/tasks/migration/</link><description>Recent content in How to smoothly migrate to the new functions of Dubbo3 on Apache Dubbo</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="https://dubbo.apache.org/en/overview/tasks/migration/index.xml" rel="self" type="application/rss+xml"/><item><title>Overview: Upgrade to Dubbo3</title><link>https://dubbo.apache.org/en/overview/tasks/migration/2to3/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/overview/tasks/migration/2to3/</guid><description> |
| <p>** Upgrade directly to Dubbo 3.0 without changing any code. **</p> |
| <p>At the beginning of the design and development of version 3.0, we set the goal of being compatible with older versions of Dubbo users (2.5, 2.6, 2.7). Therefore, the upgrade process to version 3.0 will be completely transparent, users do not need to do any business transformation, and the behavior of the framework after upgrading to version 3.x will remain completely consistent with version 2.x.</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;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.10<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></code></pre></div><p>But also note that the transparent upgrade is only the first step towards 3.0, because &ldquo;consistent framework behavior&rdquo; means that users will not be able to experience the new features of 3.0. **If you want to enable the new features brought by 3.0, users need to make some modifications. We call this process migration, which is an on-demand process. **</p> |
| <p>Therefore, for legacy users, there are two different migration paths:</p> |
| <ul> |
| <li><strong>In two steps, first promote business upgrade to version 3.0 in compatibility mode (no modification required), and then enable new features on demand at certain times (modification on demand);</strong></li> |
| <li><strong>The upgrade and migration are completed synchronously. When the business is upgraded to version 3.0, the transformation is completed and new features are enabled;</strong></li> |
| </ul> |
| <p>The new features provided by Dubbo 3.0 include:</p> |
| <ul> |
| <li>** New address discovery model (application-level service discovery). ** |
| <ul> |
| <li>See <a href="https://dubbo.apache.org/en/docs3-v2/java-sdk/upgrades-and-compatibility/service-discovery/service-discovery-samples/">Application-Level Service Discovery Migration Samples</a>.</li> |
| <li>See <a href="https://dubbo.apache.org/en/docs3-v2/java-sdk/upgrades-and-compatibility/service-discovery/migration-service-discovery/">Migration steps for application-level service discovery</a></li> |
| <li>See <a href="https://dubbo.apache.org/en/docs3-v2/java-sdk/upgrades-and-compatibility/service-discovery/service-discovery-rule/">Description of application-level service discovery address migration rules</a></li> |
| </ul> |
| </li> |
| <li>**The next generation of the HTTP/2-based Triple protocol. ** |
| <ul> |
| <li>See <a href="https://dubbo.apache.org/en/docs3-v2/java-sdk/upgrades-and-compatibility/migration-triple/">Triple Protocol Migration Steps</a></li> |
| <li>See <a href="https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/protocol/triple/guide/">Triple protocol usage</a></li> |
| <li>See <a href="https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/protocol/triple/overview/">Triple Protocol Design and Implementation</a>.</li> |
| </ul> |
| </li> |
| <li>**Unified routing rules. ** |
| <ul> |
| <li>See <a href="https://dubbo.apache.org/en/docs3-v2/java-sdk/advanced-features-and-usage/traffic/mesh-style/">Design and Implementation of Unified Routing Rules</a></li> |
| </ul> |
| </li> |
| </ul></description></item><item><title>Overview: Guide to Migrating Dubbo Protocol to Triple Protocol</title><link>https://dubbo.apache.org/en/overview/tasks/migration/migration-triple/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/overview/tasks/migration/migration-triple/</guid><description> |
| <h2 id="triple-introduction">Triple Introduction</h2> |
| <p>For the format and principle of the <code>Triple</code> protocol, please refer to <a href="https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/protocol/triple/overview/">RPC Communication Protocol</a></p> |
| <p>According to the goals of Triple design, the <code>Triple</code> protocol has the following advantages:</p> |
| <ul> |
| <li>Capable of cross-language interaction. Both the traditional multi-language and multi-SDK mode and the Mesh cross-language mode require a more general and scalable data transmission protocol.</li> |
| <li>Provide a more complete request model. In addition to supporting the traditional Request/Response model (Unary one-way communication), it also supports Stream (streaming communication) and Bidirectional (two-way communication).</li> |
| <li>Easy to expand, high penetration, including but not limited to Tracing / Monitoring and other support, should also be recognized by devices at all levels, gateway facilities, etc. can identify data packets, friendly to Service Mesh deployment, and reduce the difficulty of understanding for users.</li> |
| <li>Fully compatible with grpc, the client/server can communicate with the native grpc client.</li> |
| <li>Components in the existing grpc ecosystem can be reused to meet cross-language, cross-environment, and cross-platform intercommunication requirements in cloud-native scenarios.</li> |
| </ul> |
| <p>For Dubbo users currently using other protocols, the framework provides migration capabilities compatible with existing serialization methods. Without affecting existing online businesses, the cost of migrating protocols is almost zero.</p> |
| <p>Dubbo users who need to add new connection to Grpc service can directly use the Triple protocol to achieve the connection, and do not need to introduce the grpc client separately to complete it. Not only can the existing Dubbo ease of use be retained, but also the complexity of the program and the development and maintenance can be reduced. Cost, it can be connected to the existing ecology without additional adaptation and development.</p> |
| <p>For Dubbo users who need gateway access, the Triple protocol provides a more native way to make gateway development or use open source grpc gateway components easier. The gateway can choose not to parse the payload, which greatly improves the performance. When using the Dubbo protocol, the language-related serialization method is a big pain point for the gateway, and the traditional HTTP-to-Dubbo method is almost powerless for cross-language serialization. At the same time, since Triple&rsquo;s protocol metadata is stored in the request header, the gateway can easily implement customized requirements, such as routing and current limiting.</p> |
| <h2 id="dubbo2-protocol-migration-process">Dubbo2 protocol migration process</h2> |
| <p>Dubbo2 users use dubbo protocol + custom serialization, such as hessian2 to complete remote calls.</p> |
| <p>By default, Grpc only supports Protobuf serialization, and it cannot support multi-parameter and method overloading in the Java language.</p> |
| <p>At the beginning of Dubbo3, one goal was to be perfectly compatible with Dubbo2. Therefore, in order to ensure the smooth upgrade of Dubbo2, the Dubbo framework has done a lot of work to ensure that the upgrade is seamless. Currently, the default serialization is consistent with Dubbo2 as <code>hessian2</code>.</p> |
| <p>**So, if you decide to upgrade to Dubbo3&rsquo;s <code>Triple</code> protocol, you only need to modify the protocol name in the configuration to <code>tri</code> (note: not triple). **</p> |
| <p>For more instructions on using the <code>Triple</code> protocol, please refer to <a href="https://dubbo.apache.org/en/docs3-v2/java-sdk/upgrades-and-compatibility/migration-triple/">Triple Protocol Migration Guide</a>.</p></description></item><item><title>Overview: Dubbo3 application-level service discovery</title><link>https://dubbo.apache.org/en/overview/tasks/migration/service-discovery-samples/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/overview/tasks/migration/service-discovery-samples/</guid><description> |
| <p>Application-level service discovery is a protocol for service discovery between applications. Therefore, to use application-level service discovery, both the consumer and the server must be upgraded to Dubbo 3.0 and new features enabled (enabled by default) to use application-level service discovery in the link. Take advantage of application-level service discovery.</p> |
| <h2 id="open-method">Open method</h2> |
| <h2 id="server">Server</h2> |
| <p>After the application is upgraded to Dubbo 3.0, the server will automatically enable the interface-level + application-level dual registration function, and the developer does not need to modify any configuration by default</p> |
| <h3 id="consumer-side">Consumer side</h3> |
| <p>After the application is upgraded to Dubbo 3.0, the consumer side automatically starts the interface-level + application-level dual subscription function, and the developer does not need to modify any configuration by default. It is recommended that after the server is upgraded to Dubbo 3.0 and the application-level registration is enabled, configure the consumer end to close the interface-level subscription through rules to release the corresponding memory space.</p> |
| <h2 id="detailed-description">Detailed description</h2> |
| <h3 id="server-configuration">Server configuration</h3> |
| <ol> |
| <li>Global switch</li> |
| </ol> |
| <p>Application configuration (can be specified by configuration file or -D) <code>dubbo.application.register-mode</code> enables the global registration switch for instance (only register application level) and all (both interface level and application level registration). After configuring this switch , by default, application-level addresses will be registered with all registries for service discovery on the consumer side.</p> |
| <blockquote> |
| <p>Example: [https://github.com/apache/dubbo-samples/blob/master/dubbo-samples-cloud-native/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-provider2/src/main/resources/ dubbo.properties](<a href="https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-provider2/src">https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-provider2/src</a> /main/resources/dubbo.properties)</p> |
| </blockquote> |
| <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-fallback" data-lang="fallback"><span style="display:flex;"><span># double registration |
| </span></span><span style="display:flex;"><span>dubbo.application.register-mode=all |
| </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-fallback" data-lang="fallback"><span style="display:flex;"><span># Application-level registration only |
| </span></span><span style="display:flex;"><span>dubbo.application.register-mode=instance |
| </span></span></code></pre></div><ol start="2"> |
| <li>Registration center address parameter configuration</li> |
| </ol> |
| <p>Registry-type=service can be configured on the address of the registry to display the registry that specifies the registry as application-level service discovery, and the registry with this configuration will only perform application-level service discovery.</p> |
| <blockquote> |
| <p>Example: [https://github.com/apache/dubbo-samples/blob/master/dubbo-samples-cloud-native/dubbo-demo-servicediscovery-xml/servicediscovery-provider/src/main/resources/spring/ dubbo-provider.xml](<a href="https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-demo-servicediscovery-xml/servicediscovery-provider/src">https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-demo-servicediscovery-xml/servicediscovery-provider/src</a> /main/resources/spring/dubbo-provider.xml)</p> |
| </blockquote> |
| <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://${nacos.address:127.0.0.1}:8848?registry-type=service&#34;</span><span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><h3 id="consumer-subscription-mode">Consumer Subscription Mode</h3> |
| <p>FORCE_INTERFACE: only interface-level subscription, the behavior is consistent with Dubbo 2.7 and previous versions. |
| APPLICATION_FIRST: interface level + application level multi-subscription, if the application level can subscribe to the address, use the application level subscription, if the address cannot be subscribed, use the interface level subscription, so as to ensure the greatest compatibility during the migration process. (Note: Due to the simultaneous subscription behavior, the memory usage in this mode will increase to a certain extent, so after all servers are upgraded to Dubbo 3.0, it is recommended to migrate to FORCE_APPLICATION mode to reduce memory usage) |
| FORCE_APPLICATION: Only application-level subscriptions will only use the new service discovery model.</p> |
| <h3 id="consumer-configuration">Consumer configuration</h3> |
| <ol> |
| <li>Default configuration (no configuration required)</li> |
| </ol> |
| <p>After upgrading to Dubbo 3.0, the default behavior is interface-level + application-level multi-subscription. If the address can be subscribed at the application level, the application-level subscription will be used. If the address cannot be subscribed, the interface-level subscription will be used to ensure maximum compatibility.</p> |
| <ol start="2"> |
| <li>Subscription parameter configuration</li> |
| </ol> |
| <p>Application configuration (can be specified by configuration file or -D) <code>dubbo.application.service-discovery.migration</code> is <code>APPLICATION_FIRST</code> to enable multi-subscription mode, and configuration to <code>FORCE_APPLICATION</code> can force application-level subscription mode only. |
| The specific interface subscription can be configured in <code>parameters</code> in <code>ReferenceConfig</code>, and the Key is <code>migration.step</code>, and the Value is <code>APPLICATION_FIRST</code> or <code>FORCE_APPLICATION</code> key-value pair to configure a single subscription.</p> |
| <blockquote> |
| <p>Example: [https://github.com/apache/dubbo-samples/blob/master/dubbo-samples-cloud-native/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-consumer/src/test/java/ org/apache/dubbo/demo/consumer/DemoServiceConfigIT.java](<a href="https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-servicediscovery-migration">https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-servicediscovery-migration</a> /dubbo-servicediscovery-migration-consumer/src/test/java/org/apache/dubbo/demo/consumer/DemoServiceConfigIT.java)</p> |
| </blockquote> |
| <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>System<span style="color:#719e07">.</span>setProperty<span style="color:#719e07">(</span><span style="color:#2aa198">&#34;dubbo.application.service-discovery.migration&#34;</span><span style="color:#719e07">,</span> <span style="color:#2aa198">&#34;APPLICATION_FIRST&#34;</span><span style="color:#719e07">);</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>ReferenceConfig<span style="color:#719e07">&lt;</span>DemoService<span style="color:#719e07">&gt;</span> referenceConfig <span style="color:#719e07">=</span> <span style="color:#719e07">new</span> ReferenceConfig<span style="color:#719e07">&lt;&gt;(</span>applicationModel<span style="color:#719e07">.</span> <span style="color:#268bd2">newModule</span><span style="color:#719e07">());</span> |
| </span></span><span style="display:flex;"><span>referenceConfig<span style="color:#719e07">.</span>setInterface<span style="color:#719e07">(</span>DemoService<span style="color:#719e07">.</span>class<span style="color:#719e07">);</span> |
| </span></span><span style="display:flex;"><span>referenceConfig<span style="color:#719e07">.</span>setParameters<span style="color:#719e07">(</span><span style="color:#719e07">new</span> HashMap<span style="color:#719e07">&lt;&gt;());</span> |
| </span></span><span style="display:flex;"><span>referenceConfig<span style="color:#719e07">.</span>getParameters<span style="color:#719e07">().</span>put<span style="color:#719e07">(</span><span style="color:#2aa198">&#34;migration.step&#34;</span><span style="color:#719e07">,</span> mode<span style="color:#719e07">);</span> |
| </span></span><span style="display:flex;"><span><span style="color:#719e07">return</span> referenceConfig<span style="color:#719e07">.</span>get<span style="color:#719e07">();</span> |
| </span></span></code></pre></div><ol start="3"> |
| <li>Dynamic configuration (highest priority, configuration can be modified at runtime)</li> |
| </ol> |
| <p>This configuration needs to be pushed based on the configuration center, the Key is the application name + <code>.migration</code> (such as <code>demo-application.migraion</code>), and the Group is <code>DUBBO_SERVICEDISCOVERY_MIGRATION</code>. For details on rule body configuration, see <a href="https://dubbo.apache.org/en/docs3-v2/java-sdk/upgrades-and-compatibility/service-discovery/service-discovery-rule/">Guidelines for migrating from interface-level service discovery to application-level service discovery</a>.</p> |
| <blockquote> |
| <p>Example: [https://github.com/apache/dubbo-samples/blob/master/dubbo-samples-cloud-native/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-consumer/src/main/java/ org/apache/dubbo/demo/consumer/UpgradeUtil.java](<a href="https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-servicediscovery-migration">https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-servicediscovery-migration</a> /dubbo-servicediscovery-migration-consumer/src/main/java/org/apache/dubbo/demo/consumer/UpgradeUtil.java)</p> |
| </blockquote> |
| <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>step: FORCE_INTERFACE |
| </span></span></code></pre></div></description></item></channel></rss> |
