Dubbo (as an SDK) supports both the Dubbo protocol and the Triple protocol. The Dubbo protocol has been supported since the Dubbo 2.0 (SDK) version, while the Triple protocol was introduced in the Dubbo 3.0 (SDK) version.

The Dubbo protocol is a binary protocol that runs directly on top of TCP. Its structure can be found at https://dubbo.apache.org/en/overview/reference/protocols/tcp/.

We consider the Triple protocol to be more complex. Simply put, the Triple protocol is a "large" protocol that runs on top of HTTP and supports multiple transport types.

When the Triple protocol acts as a server, it supports exposing services via HTTP/1 (including SSE, WebSocket, etc.), HTTP/2, and HTTP/3. Regarding the content-type support specific to HTTP, we support formats including, but not limited to, application/json, text/xml, text/plain, application/octet-stream, and application/grpc. For application/grpc, in addition to the native gRPC protocol, we also support scenarios where users do not have Protobuf IDL definitions.

When the Triple protocol acts as a client, we only support requests via HTTP/2 or HTTP/3 using the application/grpc content type.

The reason for this design is that when Dubbo is exposed as a server for north-south traffic, it can be highly compatible with all clients. When Dubbo acts as a node for east-west traffic, the high-performance communication it provides by default can meet the requirements of most requests within a data center.

Therefore, from an observability perspective, we believe the rpc.protocol.name for the Triple protocol should be "Triple," and for the Dubbo protocol, it should be "Dubbo." Additionally, we hope that under the Triple protocol, an extra field can be used to indicate to the user whether the request's content-type is application/json, text/xml, text/plain, application/octet-stream, or application/grpc.

Decide on which rpc.protocol.name values to mark stable as part of initial RPC semconv stability #2921

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Decide on which `rpc.protocol.name` values to mark stable as part of initial RPC semconv stability #2921