Sentinel integration for Apache Dubbo

Clone this repo:


  1. 751e796 Sync code and bump version to 1.6.0 by Eric Zhao · 1 year, 5 months ago master
  2. 5da4ee5 Bump version to 1.4.2 by Eric Zhao · 1 year, 7 months ago
  3. e9f2dab Bump version to 1.3.0-GA by Eric Zhao · 1 year, 11 months ago
  4. 73d5647 Enhance exception tracing in Sentinel Dubbo Adapter by Eric Zhao · 2 years ago
  5. 3d580a1 Sync update and bump version to 0.1.1 by Eric Zhao · 2 years, 1 month ago

Sentinel Apache Dubbo Adapter

Note: 中文文档请见此处

Sentinel Dubbo Adapter provides service consumer filter and provider filter for Apache Dubbo services.

Note: This adapter only supports Apache Dubbo 2.7.x and above. For legacy 2.6.x, please use sentinel-dubbo-adapter module instead.

To use Sentinel Dubbo Adapter, you can simply add the following dependency to your pom.xml:


The Sentinel filters are enabled by default. Once you add the dependency, the Dubbo services and methods will become protected resources in Sentinel, which can leverage Sentinel's flow control and guard ability when rules are configured. Demos can be found in sentinel-demo-dubbo.

If you don't want the filters enabled, you can manually disable them. For example:

<dubbo:consumer filter="-sentinel.dubbo.consumer.filter"/>

<dubbo:provider filter="-sentinel.dubbo.provider.filter"/>

For more details of Dubbo filter, see here.

Dubbo resources

The resource for Dubbo services has two granularities: service interface and service method.

  • Service interface:resourceName format is interfaceName,e.g.
  • Service method:resourceName format is interfaceName:methodSignature,e.g.

Flow control based on caller

In many circumstances, it's also significant to control traffic flow based on the caller. For example, assuming that there are two services A and B, both of them initiate remote call requests to the service provider. If we want to limit the calls from service B only, we can set the limitApp of flow rule as the identifier of service B (e.g. service name).

Sentinel Dubbo Adapter will automatically resolve the Dubbo consumer‘s application name as the caller’s name (origin), and will bring the caller's name when doing resource protection. If limitApp of flow rules is not configured (default), flow control will take effects on all callers. If limitApp of a flow rule is configured with a caller, then the corresponding flow rule will only take effect on the specific caller.

Note: Dubbo consumer does not provide its Dubbo application name when doing RPC, so developers should manually put the application name into attachment at consumer side, then extract it at provider side. Sentinel Dubbo Adapter has implemented a filter (DubboAppContextFilter) where consumer can carry application name information to provider automatically. If the consumer does not use Sentinel Dubbo Adapter but requires flow control based on caller, developers can manually put the application name into attachment with the key dubboApplication.

Global fallback

Sentinel Dubbo Adapter supports global fallback configuration. The global fallback will handle exceptions and give replacement result when blocked by flow control, degrade or system load protection. You can implement your own DubboFallback interface and then register to DubboFallbackRegistry. If no fallback is configured, Sentinel will wrap the BlockException then directly throw it out.

Besides, we can also leverage Dubbo mock mechanism to provide fallback implementation of degraded Dubbo services.