| <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Apache Dubbo – Tasks</title><link>https://dubbo.apache.org/en/overview/tasks/</link><description>Recent content in Tasks on Apache Dubbo</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="https://dubbo.apache.org/en/overview/tasks/index.xml" rel="self" type="application/rss+xml"/><item><title>Overview: Traffic Management</title><link>https://dubbo.apache.org/en/overview/tasks/traffic-management/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/overview/tasks/traffic-management/</guid><description> |
| <section id="section-0" style=""> |
| <div class="td-content list-page"> |
| <div class="lead"></div><header class="article-meta"> |
| </header><div class="row"> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow" href="#"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/traffic-management/timeout/'>Dynamically adjust request timeout</a> |
| </h4> |
| <p>Setting a timeout period for Dubbo requests can effectively improve system stability and prevent individual services from being blocked and occupying too many resources. <br/><br/>By dynamically adjusting the service timeout period during the running period, it can effectively deal with problems such as frequent service timeouts and service blocking caused by unreasonable timeout settings and system emergencies, and improve system stability. </p> |
| </div> |
| </div> |
| </div> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/traffic-management/weight/'>Adjust traffic distribution by weight</a> |
| </h4> |
| <p>Adjust traffic distribution by weight</p> |
| </div> |
| </div> |
| </div> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/traffic-management/isolation/'>Temporarily kick the service instance</a> |
| </h4> |
| <p>Temporarily kick the service instance</p> |
| </div> |
| </div> |
| </div> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/traffic-management/traffic-gray/'>traffic grayscale</a> |
| </h4> |
| <p>According to the tags in the request context, the traffic is restricted and the grayscale release</p> |
| </div> |
| </div> |
| </div> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/traffic-management/traffic-routing/'>Routing according to request conditions</a> |
| </h4> |
| <p>Routing according to the request initiator and method condition</p> |
| </div> |
| </div> |
| </div> |
| <div class="col-sm col-md-6 mb-4 mb-md-0" style="margin-bottom:20px"> |
| <div class="h-100 card shadow"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/traffic-management/traffic-condition/'>Traffic isolation</a> |
| </h4> |
| <p>Isolate service traffic in different environments to ensure that services are not affected by each other</p> |
| </div> |
| </div> |
| </div> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/traffic-management/zone/'>Same computer room/zone priority</a> |
| </h4> |
| <p>When an application invokes a service, it preferentially invokes the service provider in the same computer room/area. </p> |
| </div> |
| </div> |
| </div> |
| </div> |
| <hr> |
| </div> |
| </section></description></item><item><title>Overview: Kubernetes Deployment Solution</title><link>https://dubbo.apache.org/en/overview/tasks/kubernetes/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/overview/tasks/kubernetes/</guid><description> |
| <section id="section-0" style=""> |
| <div class="td-content list-page"> |
| <div class="lead"></div><header class="article-meta"> |
| </header><div class="row"> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow" href="#"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/kubernetes/deploy-on-k8s/'>API-SERVER</a> |
| </h4> |
| <p>Use API-SERVER as the registration center, deploy Dubbo application to Kubernetes and reuse Kubernetes Native Service example</p> |
| </div> |
| </div> |
| </div> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow" href="#"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/mesh/'>Dubbo Mesh</a> |
| </h4> |
| <p>Through the Dubbo Control Plane, the details of service governance are shielded, while retaining the native ability to adapt to kubernetes, the decoupling of the data plane and kubernetes is realized from the architecture, and various problems caused by direct communication between the data plane and kubernetes are avoided. <br/><br/>For details, please refer to the Mesh solution section</p> |
| </div> |
| </div> |
| </div> |
| </div> |
| <hr> |
| </div> |
| </section></description></item><item><title>Overview: Mesh Deployment Solution</title><link>https://dubbo.apache.org/en/overview/tasks/mesh/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/overview/tasks/mesh/</guid><description> |
| <section id="section-0" style=""> |
| <div class="td-content list-page"> |
| <div class="lead"></div><header class="article-meta"> |
| </header><div class="row"> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow" href="#"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/mesh/dubbo-mesh/'>Istio + Sidecar + Thin SDK</a> |
| </h4> |
| <p>Demonstration of Dubbo3's Sidecar Mesh form, which can fully access Istio's service governance capabilities. This solution limits Dubbo3 application-level service discovery. </p> |
| </div> |
| </div> |
| </div> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/mesh/dubbo-mesh/'>Istio + Proxyless</a> |
| </h4> |
| <p>The Dubbo3 Proxyless Mesh form without Sidecar can fully access the service management capability of Istio. This solution limits Dubbo3 application-level service discovery. </p> |
| </div> |
| </div> |
| </div> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <!-- <a href='https://dubbo.apache.org/en/overview/tasks/mesh/dubbo-mesh/'>Dubbo Control Plane + Thin SDK (TBD)</a> --> |
| <p>Dubbo Control Plane + Thin SDK (document construction)</p> |
| </h4> |
| <p></p> |
| </div> |
| </div> |
| </div> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <!-- <a href='https://dubbo.apache.org/en/overview/tasks/mesh/dubbo-mesh/'>Dubbo Control Plane + Proxyless (TBD)</a> --> |
| <p>Dubbo Control Plane + Proxyless (document construction)</p> |
| </h4> |
| <p></p> |
| </div> |
| </div> |
| </div> |
| </div> |
| <hr> |
| </div> |
| </section></description></item><item><title>Overview: Triple Usage Example</title><link>https://dubbo.apache.org/en/overview/tasks/triple/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/overview/tasks/triple/</guid><description> |
| <section id="section-0" style=""> |
| <div class="td-content list-page"> |
| <div class="lead"></div><header class="article-meta"> |
| </header><div class="row"> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow" href="#"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/triple/idl/'>Define a service using IDL</a> |
| </h4> |
| <p>Using IDL to define cross-language services</p> |
| </div> |
| </div> |
| </div> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow" href="#"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/triple/wrap/'>Pojo serialization compatibility mode</a> |
| </h4> |
| <p>Pojo serialization compatibility mode</p> |
| </div> |
| </div> |
| </div> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow" href="#"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/triple/streaming/'>Streaming communication</a> |
| </h4> |
| <p>Stream communication mode</p> |
| </div> |
| </div> |
| </div> |
| </div> |
| <hr> |
| </div> |
| </section></description></item><item><title>Overview: How to smoothly migrate to the new functions of Dubbo3</title><link>https://dubbo.apache.org/en/overview/tasks/migration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/overview/tasks/migration/</guid><description> |
| <section id="section-0" style=""> |
| <div class="td-content list-page"> |
| <div class="lead"></div><header class="article-meta"> |
| </header><div class="row"> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow" href="#"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/migration/2to3/'>Smooth upgrade to Dubbo3</a> |
| </h4> |
| <p>Smoothly upgrade to Dubbo3 version. </p> |
| </div> |
| </div> |
| </div> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/migration/service-discovery-samples/'>Migrate to Dubbo3 application-level service discovery</a> |
| </h4> |
| <p>Migrate to Dubbo3 application-level service discovery. </p> |
| </div> |
| </div> |
| </div> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/migration/migration-triple/'>Migrate to Triple Protocol</a> |
| </h4> |
| <p>Migrate to Dubbo3 Triple protocol</p> |
| </div> |
| </div> |
| </div> |
| </div> |
| <hr> |
| </div> |
| </section></description></item><item><title>Overview: Microservice Governance</title><link>https://dubbo.apache.org/en/overview/tasks/ecosystem/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/overview/tasks/ecosystem/</guid><description> |
| <section id="section-0" style=""> |
| <div class="td-content list-page"> |
| <div class="lead"></div><header class="article-meta"> |
| </header><div class="row"> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow" href="#"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/ecosystem/transaction/'>Transaction Management</a> |
| </h4> |
| <p>This example demonstrates how to implement transaction management of distributed Dubbo services through Seata to ensure data consistency. </p> |
| </div> |
| </div> |
| </div> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/ecosystem/rate-limit/'>rate limit downgrade</a> |
| </h4> |
| <p>Use Sentinel to protect your application from stability issues caused by sudden traffic overload of individual services. </p> |
| </div> |
| </div> |
| </div> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <p>http gateway access (document construction)</p> |
| </h4> |
| <p>By converting the gateway http to dubbo protocol, the front-end traffic can be connected to the back-end dubbo service. </p> |
| </div> |
| </div> |
| </div> |
| <div class="col-sm col-md-6 mb-4 mb-md-0"> |
| <div class="h-100 card shadow"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <p>Spring Cloud system interoperability (document construction)</p> |
| </h4> |
| <p>Demonstrates how to communicate with Spring Cloud's rest protocol through the Dubbo3 application-level service discovery mechanism. </p> |
| </div> |
| </div> |
| </div> |
| </div> |
| <hr> |
| </div> |
| </section></description></item><item><title>Overview: Custom Extensions</title><link>https://dubbo.apache.org/en/overview/tasks/extensibility/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/overview/tasks/extensibility/</guid><description> |
| <h2 id="dubbos-extensibility-design-philosophy">Dubbo&rsquo;s Extensibility Design Philosophy</h2> |
| <ul> |
| <li>Equality towards third-party implementations: In Dubbo, all internal and external implementations are treated equally. Users can replace Dubbo&rsquo;s native implementations based on their business requirements.</li> |
| <li>Each extension point encapsulates only one variable factor for maximum reuse: The implementer of each extension point is often only concerned with one thing. If users need to extend functionality, they only need to extend the relevant extension points, significantly reducing the workload.</li> |
| </ul> |
| <h2 id="java-spi-based-extensibility-design">Java SPI-based Extensibility Design</h2> |
| <p>Dubbo&rsquo;s extensibility comes from an enhanced version of the JDK standard SPI (Service Provider Interface). It improves upon the following issues with the JDK&rsquo;s standard SPI:</p> |
| <ul> |
| <li>The standard SPI instantiates all extension points at once, wasting resources if some are not used.</li> |
| <li>If extension point loading fails, even the name of the extension point cannot be retrieved.</li> |
| </ul> |
| <p>Dubbo&rsquo;s extensibility features:</p> |
| <ul> |
| <li>On-demand loading: Dubbo doesn&rsquo;t instantiate all implementations at once, reducing resource waste.</li> |
| <li>IOC (Inversion of Control) capabilities: Dubbo not only discovers extension service implementation classes but also automatically injects dependent objects into the extension class.</li> |
| <li>AOP (Aspect-Oriented Programming) capabilities: Dubbo automatically discovers wrapper classes for extensions, constructing them to enhance extension functionality.</li> |
| <li>Dynamic extension selection: Dubbo dynamically chooses the corresponding extension class based on parameters at runtime.</li> |
| <li>Extension implementation sorting: Users can specify the execution order of extension implementations.</li> |
| <li>Adaptive extension points: Extensions can be made effective on either the consumer or provider side.</li> |
| </ul> |
| <h3 id="extension-loading-process">Extension Loading Process</h3> |
| <p>Dubbo&rsquo;s extension loading process is as follows:</p> |
| <p><img src="https://dubbo.apache.org/imgs/v3/concepts/extension-load.png" alt="//imgs/v3/concepts/extension-load.png"></p> |
| <p>The main steps are:</p> |
| <ul> |
| <li>Read and parse the configuration file</li> |
| <li>Cache all extension implementations</li> |
| <li>Instantiate the corresponding extension implementation based on the user-executed extension name</li> |
| <li>Perform IOC injection for extension instance attributes and instantiate extension wrapper classes for AOP features</li> |
| </ul> |
| <h2 id="task-items">Task Items</h2> |
| <p>Next, let&rsquo;s introduce Dubbo&rsquo;s extensibility features through the following task items.</p> |
| <section id="section-0" style=""> |
| <div class="td-content list-page"> |
| <div class="lead"></div><header class="article-meta"> |
| </header><div class="row"> |
| <div class="col-sm col-md-6 mb-4"> |
| <div class="h-100 card shadow" href="#"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/extensibility/filter/'>Custom Filters</a> |
| </h4> |
| <p>Dynamically load custom filters through the SPI mechanism to uniformly handle, validate returned results, and minimize developer interruptions.</p> |
| </div> |
| </div> |
| </div> |
| <div class="col-sm col-md-6 mb-4"> |
| <div class="h-100 card shadow"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/extensibility/router/'>Custom Routing</a> |
| </h4> |
| <p>Customize routing strategies during service invocation based on actual use-cases to effectively improve service throughput and latency.</p> |
| </div> |
| </div> |
| </div> |
| <div class="col-sm col-md-6 mb-4"> |
| <div class="h-100 card shadow"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/extensibility/protocol/'>Custom Protocols</a> |
| </h4> |
| <p>Use custom transport protocols for different heterogeneous systems to eliminate the differences between protocols and facilitate system integration.</p> |
| </div> |
| </div> |
| </div> |
| <div class="col-sm col-md-6 mb-4"> |
| <div class="h-100 card shadow"> |
| <div class="card-body"> |
| <h4 class="card-title"> |
| <a href='https://dubbo.apache.org/en/overview/tasks/extensibility/registry/'>Custom Registry Centers</a> |
| </h4> |
| <p>Include services from different registry centers into the Dubbo ecosystem. Customizing registry centers is a key to bridging different service ecosystems.</p> |
| </div> |
| </div> |
| </div> |
| </div> |
| <hr> |
| </div> |
| </section> |
| <p>Dubbo&rsquo;s extensibility design aims to provide users with a highly flexible extension mechanism, offering features like dynamic extension selection, IOC, and AOP. This makes it easier to adapt Dubbo to various scenarios and integrate it into different technology stacks.</p></description></item></channel></rss> |
