New features

New features

New features of Dubbo-go 3.0

1. Triple Protocol

1.1 Overview

Communication level

The Triple protocol, also known as the Dubbo3 protocol, is an extended protocol based on HTTP2 + gRPC, which adds specific fields and logical enhancements, ensuring interoperability with the native gRPC protocol. On this basis, the Triple new protocol will more natively support Dubbo service governance capabilities and support streaming RPC calls.

In simple terms, it can be understood as Triple = gRPC + Dubbo.
Serialization

The Triple protocol uses an efficient PB serialization method and adds extensible support for serialization protocols.
User development habits:

Triple services require pre-defined .proto files before development, which facilitates Go developers who prefer to define IDL before coding. This differs from the Dubbo-go 1.x version that defines JavaClassName to describe interfaces in line with Java programming habits.
Cross-language interoperability:

It can achieve cross-language interoperability with Dubbo-Java.

2. Application-level Service Discovery

2.1 Introduction

During the service registration phase, server instances register application-level information, mainly mapping application names to instance IPs in the registration center. In the service discovery phase, client instances obtain the required service instance IP through the registration center. The service introspection phase follows, where the process of service introspection involves obtaining interface information through application information. As shown in the figure, there are two modes:

remote mode: obtaining application to interface metadata mapping through a metadata center (e.g., zk).
local mode: obtaining application to interface metadata mapping directly from the server (initiating an RPC call to the Metadata Service through the Dubbo protocol).

After service introspection, the client officially initiates a call to the corresponding instance. The most obvious benefit of this approach is the reduced data volume for the registration center, which only retains application-level data.

When using Dubbo-go 3.0’s application-level service discovery capabilities, users can follow the examples to configure the service introspection mode and metadata center information directly in the configuration file, add dependencies, and enable application-level service discovery.