Dubbo SPI Overview

Dubbo provides very flexible extensibility through the SPI mechanism

Using IoC containers to help manage the lifecycle of components, dependency injection, etc., is a common design in many development frameworks. Dubbo has a lightweight version of an IoC container built in, used to manage plugins within the framework, achieving capabilities such as plugin instantiation, lifecycle management, and automatic dependency injection.

Readers interested may learn about:

The Dubbo plugin system and IoC container have the following characteristics:

  • Core components are defined as plugins, making it very easy for users or secondary developers to expand. Users can extend strategies like load balancing, registration centers, communication protocols, routing, etc., based on their needs without modifying the framework kernel.
  • Treating third-party extensions equally. All internal and third-party implementations in Dubbo are treated the same, allowing users to replace the native implementations provided by Dubbo according to their business needs.
  • Plugin dependencies support automatic injection (IoC). If a plugin implementation depends on other plugin properties, the Dubbo framework will automatically inject that dependent object, supporting methods like properties and constructors.
  • Plugin extension implementations support AOP capabilities. The framework can automatically discover wrapper classes for extension classes and enhance the plugin using AOP through the wrapper pattern.
  • Automatic plugin activation is supported. By specifying activation conditions for plugin implementations (through annotation parameters, etc.), the framework can automatically decide whether to activate that plugin implementation based on the current context at runtime.
  • Support for plugin extension sorting.

Feedback

Was this page helpful?

Yes No

Last modified September 30, 2024: Update & Translate Overview Docs (#3040) (d37ebceaea7)