How Dubbo’s Triple X Protocol Leverages HTTP/3 for 6× Faster RPC in Weak Networks

Background and Motivation

In early versions, Apache Dubbo excelled at high‑performance service communication within data‑center environments, but its original architecture showed bottlenecks when workloads expanded to cross‑region, cross‑cloud, and micro‑service scenarios. The traditional RPC model struggled with north‑south traffic optimization, lacked native HTTP support, and offered limited language‑agnostic interoperability.

Triple X Protocol: Design Goals and Breakthroughs

The Triple X protocol was created to address these pain points. It retains Dubbo’s high‑throughput communication while adding full compatibility with gRPC and supporting HTTP/1, HTTP/2, and the newly added HTTP/3. This enables flexible, efficient communication for cloud‑native, multi‑region deployments.

Why HTTP/3 Matters for RPC

Reduced latency and faster connection establishment, especially on mobile or long‑distance links.

Multiplexed streams share a single UDP‑based QUIC connection, eliminating head‑of‑line blocking.

Built‑in TLS 1.3 provides mandatory encryption with simplified configuration.

Robust handling of packet loss keeps RPC performance stable in unreliable networks.

Performance and Reliability Benefits

Improved performance: QUIC‑based transport cuts round‑trip time, accelerating response times in high‑latency environments.

Enhanced reliability: Multiplexing and connection migration avoid stalls, maintaining stable service delivery.

Higher security: Mandatory TLS 1.3 encryption offers stronger protection than optional TLS in HTTP/2.

Adaptation to weak networks: HTTP/3 sustains throughput under high packet‑loss or fluctuating bandwidth conditions.

Enabling HTTP/3 in Dubbo

To activate HTTP/3, the application must use the Triple RPC protocol and add a few configuration entries.

dubbo:</code>
<code>  protocol:</code>
<code>    name: tri</code>
<code>    triple:</code>
<code>      http3:</code>
<code>        enabled: true

Additionally, include the QUIC codec dependency and, if needed, a BouncyCastle library for self‑signed certificates:

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

Practical Example

The dubbo-samples repository contains a complete demo under 2-advanced/dubbo-samples-triple-http3. After applying the configuration above, start the sample; it will communicate over HTTP/3.

Test the service with a recent curl that supports HTTP/3:

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

Typical output shows QUIC cipher selection, HTTP/3 stream establishment, and a JSON response “Hello world”.

Benchmark Results

Performance tests in weak‑network conditions (high packet loss, limited bandwidth) demonstrated up to a six‑fold increase in QPS and markedly lower response times when using HTTP/3 compared with HTTP/2.

Architecture Overview

The following diagram illustrates how Triple X integrates HTTP/1, HTTP/2, and HTTP/3 within Dubbo’s RPC stack.

Conclusion

By incorporating HTTP/3, Apache Dubbo’s Triple X protocol delivers substantial latency reduction, higher throughput, and stronger security for distributed services, especially in cross‑cloud, cross‑region, and lossy‑network environments. The seamless compatibility with HTTP/1 and HTTP/2 also gives developers flexibility to adopt the most suitable transport for their use case.