Advanced Dubbo Architecture and Service Invocation Process

Dubbo is a Java‑based RPC framework whose architecture consists of four main roles: consumer, provider, registry and monitoring system.

The interaction flow begins with the consumer obtaining provider information from the registry, establishing a connection via Dubbo’s client SDK, and invoking remote methods; the provider receives the request through its server SDK, processes it, and returns the result.

Service calls involve encoding the request, sending it over the network (Netty by default), decoding on the server side, dispatching to a thread pool, executing the target service, and finally returning the response to the consumer’s thread.

Dubbo’s design relies on a microkernel‑plus‑plugin model, where the core kernel assembles plugins and all functionality is exposed as extensible SPI points; configuration is unified through URL parameters.

The SPI mechanism is implemented by the ExtensionLoader class, which loads extension classes from META‑INF/dubbo, creates instances via reflection, injects dependencies, and wraps them when necessary.

Key SPI concepts include the @SPI annotation for defining extension points, @Adaptive for generating adaptive extensions that are loaded based on runtime parameters, and @Activate for conditional activation of extensions.

An example demonstrates defining a Hello interface, configuring its implementation in a properties file, and loading it through

ExtensionLoader.getExtensionLoader(Hello.class).getExtension("impl")

.

The article also explains the thread‑dispatch strategies (all, direct, etc.), the role of wrappers, setter‑based dependency injection, and how Dubbo enhances the standard Java SPI to support AOP and caching.