Asynchronous call

Initiate an asynchronous call in Dubbo

Feature description


Starting from 2.7.0, all asynchronous programming interfaces of Dubbo are based on CompletableFuture

Based on NIO’s non-blocking implementation of parallel calls, the client does not need to start multi-threads to complete parallel calls to multiple remote services, and the overhead of multi-threading is relatively small.


Reference use case

scenes to be used

Send the user request content to the target request. When the target request encounters high traffic or needs to be processed for a long time, the asynchronous call function will allow the response to be returned to the user immediately, while the target request continues to process the request in the background. When the target request returns the result, the content will be sent displayed to the user.

How to use

Interface signed with CompletableFuture

For services that require service providers to define CompletableFuture signatures in advance, the interface definition guidelines are as follows:

The asynchronous execution of the provider side switches the blocked business from Dubbo’s internal thread pool to the business-defined thread, avoiding excessive occupation of the Dubbo thread pool, and helping to avoid the mutual influence between different services. Asynchronous execution is tantamount to saving resources or improving RPC response performance, because if business execution needs to be blocked, there is always a thread to be responsible for execution.

Provider-side asynchronous execution and Consumer-side asynchronous call are independent of each other, any orthogonal combination of two configurations

  • Consumer Synchronization - Provider Synchronization
  • Consumer asynchronous - Provider synchronous
  • Consumer synchronous - Provider asynchronous
  • Consumer asynchronous - Provider asynchronous

Define the interface of CompletableFuture signature

service interface definition

public interface AsyncService {
    CompletableFuture<String> sayHello(String name);

service realization

public class AsyncServiceImpl implements AsyncService {
    public CompletableFuture<String> sayHello(String name) {
        return CompletableFuture. supplyAsync(() -> {
            try {
                Thread. sleep(5000);
            } catch (InterruptedException e) {
            return "async response from provider.";

Through return CompletableFuture.supplyAsync(), the business execution has been switched from the Dubbo thread to the business thread, avoiding the blocking of the Dubbo thread pool.

Using AsyncContext

Dubbo provides an asynchronous interface AsyncContext similar to Servlet 3.0, which can also implement asynchronous execution on the Provider side without the CompletableFuture signature interface.

service interface definition

public interface AsyncService {
    String sayHello(String name);

Service exposure, exactly the same as ordinary services

<bean id="asyncService" class="org.apache.dubbo.samples.governance.impl.AsyncServiceImpl"/>
<dubbo:service interface="org.apache.dubbo.samples.governance.api.AsyncService" ref="asyncService"/>

service realization

public class AsyncServiceImpl implements AsyncService {
    public String sayHello(String name) {
        final AsyncContext asyncContext = RpcContext. startAsync();
        new Thread(() -> {
            // If you want to use the context, it must be executed in the first sentence
            try {
                Thread. sleep(500);
            } catch (InterruptedException e) {
            // write back the response
            asyncContext.write("Hello " + name + ", response from provider.");
        return null;

Note that the return type of the interface is CompletableFuture<String>.

XML Reference Service

<dubbo:reference id="asyncService" timeout="10000" interface=""/>

call remote service

// The call directly returns CompletableFuture
CompletableFuture<String> future = asyncService.sayHello("async call request");
// add callback
future. whenComplete((v, t) -> {
    if (t != null) {
        t. printStackTrace();
    } else {
        System.out.println("Response: " + v);
// earlier than the result output
System.out.println("Executed before response return.");

Using RpcContext

Configure in consumer.xml

<dubbo:reference id="asyncService" interface="org.apache.dubbo.samples.governance.api.AsyncService">
      <dubbo:method name="sayHello" async="true" />

calling code

// this call returns null immediately
// Get the Future reference of the call, when the result is returned, it will be notified and set to this Future
CompletableFuture<String> helloFuture = RpcContext.getServiceContext().getCompletableFuture();
// add callback for Future
helloFuture. whenComplete((retValue, exception) -> {
    if (exception == null) {
    } else {
        exception. printStackTrace();

Alternatively, it is also possible to do this asynchronously by calling

CompletableFuture<String> future = RpcContext.getServiceContext().asyncCall(
    () -> {
        asyncService.sayHello("oneway call request1");

future. get();

Asynchronous always does not wait for return, you can also set whether to wait for the message to be sent

  • sent="true" waits for the message to be sent, and an exception will be thrown if the message fails to be sent.
  • sent="false" does not wait for the message to be sent, puts the message in the IO queue, and returns immediately.
<dubbo:method name="findFoo" async="true" sent="true" />

If you just want to be asynchronous and completely ignore the return value, you can configure return="false" to reduce the cost of creating and managing Future objects

<dubbo:method name="findFoo" async="true" return="false" />

Last modified January 2, 2023: Enhance en docs (#1798) (95a9f4f6c1c)