Traffic Control on Apache Dubbo

Affinity Router

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

Condition Router

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

How to use

Prerequisites

Docker and Docker Compose environment to deploy Nacos registry.
Nacos Version 2.x+
Go 1.23+

Run Nacos

Follow this instruction to install and start Nacos server.

Condition router

Similar to the Tag Router, the condition router offers more advanced traffic control capabilities. It uses consumer => provider expressions to manage traffic for both providers and consumers.

Expression example:

host = 127.0.0.1 => host = 127.0.0.1, 192.168.1.1

You can use = and != symbols for matching, and use commas for multiple choice matching.

Script Router

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

How to use

Prerequisites

Docker and Docker Compose environment to deploy Nacos registry.
Nacos Version 2.x+
Go 1.23+

Run Nacos

Follow this instruction to install and start Nacos server.

Script router

Similar to the condition router, the script router enables traffic control using expressions. However, while it offers more powerful matching capabilities, this comes at the cost of higher resource consumption. Therefore, it should be used sparingly in production environments.

The example code for the script router is similar to that of the condition router, with slight differences in the Nacos configuration. Therefore, only the Nacos configuration is provided here.

Tag Router

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

How to use

Prerequisites

Docker and Docker Compose environment to deploy Nacos registry.
Nacos Version 2.x+
Go 1.23+

Run Nacos

Follow this instruction to install and start Nacos server.

Tag router

The tag router enables traffic control based on tags. The following is the example code.

Server side:

ins, err := dubbo.NewInstance(
		dubbo.WithName("tag-server"),
		dubbo.WithTag("test-Tag"), // set application's tag
		dubbo.WithRegistry(
			registry.WithNacos(),
			registry.WithAddress(RegistryAddress),
		),
		dubbo.WithProtocol(
			protocol.WithTriple(),
			protocol.WithPort(20000),
		),
	)

Parameters:

Sentinel Rate Limiting and Downgrade

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

Dubbo-go provides a built-in rate limiting component, allowing users to adjust rate limiting values and post-limiting behaviors according to their business scenarios. The specifics can be defined and implemented in TpsLimiter. Users can set a simple rate limiting strategy on the server side in a manner similar to the following:

server.WithTpsLimiter("method-service") // Currently supports implementations like method-service, polaris, etc.
server.WithTpsLimiterXxx() // Set rate limiting related thresholds, please fill in according to the specific method
//tps.limit.strategy: "slidingWindow"
//tps.limit.rejected.handler: "default"
//tps.limit.interval: 1000
//tps.limit.rate: 3

The built-in rate limiting strategy in Dubbo-go is relatively simple. For more complex scenarios, we recommend using professional third-party frameworks like Sentinel to achieve richer and more flexible rate limiting strategies.