Apache Dubbo Triple X Protocol Adds Full HTTP/3 Support: Design, Configuration, and Performance

Since version 3.3.0, Apache Dubbo has introduced the Triple X protocol, which natively supports HTTP/1, HTTP/2 and the newly added HTTP/3, providing a unified RPC solution for cloud‑native applications.

Traditional Dubbo deployments, optimized for data‑center environments, encounter bottlenecks when crossing regions or clouds, especially regarding north‑south versus east‑west traffic, and lack native HTTP and multi‑language interoperability.

Triple X addresses these issues by retaining Dubbo's high‑performance communication while adding full compatibility with gRPC and enabling seamless operation over HTTP/1, HTTP/2 and HTTP/3.

HTTP/3, built on QUIC, brings low latency, connection migration, multiplexing, mandatory TLS 1.3 encryption and robust loss‑tolerance, which together dramatically improve RPC response times, concurrency and security, particularly in mobile or high‑latency networks.

To enable HTTP/3, add the following configuration to the Dubbo YAML file:

dubbo:
    protocol:
        name: tri
        triple:
            http3:
                enabled: true

and include the required dependencies:

<dependencies>
    <dependency>
        <groupId>io.netty.incubator</groupId>
        <artifactId>netty-incubator-codec-http3</artifactId>
        <version>0.0.28.Final</version>
    </dependency>
    <dependency>
        <groupId>org.bouncycastle</groupId>
        <artifactId>bcpkix-jdk15on</artifactId>
        <version>1.70</version>
    </dependency>
</dependencies>

After rebuilding, the sample in dubbo-samples-triple-http3 can be started, and the service can be tested with a HTTP/3‑capable curl command:

curl --http3 -vk 'https://localhost:50052/org.apache.dubbo.demo.GreeterService/sayHelloAsync?request=world'

Benchmarks show that in weak‑network conditions the Triple X protocol with HTTP/3 achieves up to a six‑fold increase in QPS and markedly lower response times compared with HTTP/2.

Architecture diagrams (included as images) illustrate how the Triple X stack routes requests through the QUIC layer, enabling automatic fallback from HTTP/2 to HTTP/3 via Alt‑Svc negotiation.

In summary, the integration of HTTP/3 into Dubbo's Triple X protocol expands cross‑cloud and cross‑region capabilities, improves latency, reliability and security, and solidifies Dubbo’s position as a leading high‑performance RPC framework for modern microservice architectures.