Technical Solutions on Apache Dubbo

Dubbo3 Application-Level Service Discovery Design

Mon, 30 Jan 2023 00:00:00 +0000

Objective

Significantly reduce resource consumption during the service discovery process, including increasing the registration center’s capacity limit and reducing resource usage for consumer address resolution, allowing the Dubbo3 framework to support larger-scale cluster service governance and achieve unlimited horizontal scalability.
Adapt to underlying infrastructure service discovery models such as Kubernetes, Service Mesh, etc.

Background

We start with the classic working principle diagram of Dubbo; from its design inception, Dubbo has built-in capabilities for service address discovery. Providers register their addresses with the registration center, and consumers subscribe to receive real-time updates about address changes from the registration center. Upon receiving the address list, consumers initiate RPC calls to providers based on specific load balancing strategies.

Heuristic Flow Control

Mon, 30 Jan 2023 00:00:00 +0000

Overview

The flexible services discussed in this article primarily refer to load balancing on the consumer side and rate limiting on the provider side. In previous versions of Dubbo,

The load balancing component primarily focused on the principle of fairness, meaning that the consumer would choose from providers as equally as possible, which did not perform ideally in certain situations.
The rate limiting component provided only static rate limiting schemes, requiring users to set static maximum concurrency values on the provider side, which are not easy for users to select reasonably.

We have made improvements to address these issues.

Enhanced HTTP Standard Capabilities of Triple Protocol

Mon, 01 Jan 0001 00:00:00 +0000

Enhanced HTTP Standard Capabilities of Triple Protocol - Support for Multiple Content-Type

This article focuses on how Triple supports more of the HTTP standard Content-Type and how the service receives these requests.

Overview

Triple currently supports two serialization methods: Json and protobuf, corresponding to the ContentTypes:

application/json
application/grpc+proto

This poses no issue when both the consumer and provider are backend services. However, for browser clients, they may send a wider variety of ContentTypes, which requires server-side support for decoding, such as: