Detailed Explanation of the Dubbo RPC Call Process from Consumer to Provider

The consumer side starts by declaring a remote service reference in Spring configuration, for example:

<dubbo:reference id="demoService" interface="com.alibaba.dubbo.demo.DemoService"/>

When demoService.sayHello("world!") is invoked, the call is routed to InvokerInvocationHandler.invoke, which creates an RpcInvocation containing the method name and arguments. The request then passes through the MockClusterInvoker (choosing mock or real invocation) and the default FailoverClusterInvoker, which discovers all provider invokers via the registry, applies routing rules, and selects one invoker using the configured LoadBalance strategy.

The selected DubboInvoker builds an ExchangeClient based on the provider's URL, determines the call mode (sync, async, or oneway), and sends the invocation over the network. The response handling varies: oneway returns an empty RpcResult, async returns a ResponseFuture, and sync blocks until the result is received.

On the provider side, the incoming request is handled by DubboProtocol.requestHandler, which extracts the service key and retrieves the corresponding DubboExporter and its Invoker. The request then traverses the filter and listener chains before reaching the actual service implementation via the proxy created by ProxyFactory.getInvoker. The service method executes, and the result is wrapped in an RpcResult and sent back through the DubboProtocol response path.

Underlying network communication is performed by Netty: the provider's HeaderExchangeServer (built by NettyTransporter) listens on a socket, decodes the incoming HeaderExchangeHandler messages, and forwards them to the Dubbo protocol handler. The client uses HeaderExchangeChannel and NettyChannel to transmit the request.

Additional code excerpts illustrate the lifecycle of a Spring ClassPathXmlApplicationContext, the export process in ServiceConfig, and the creation of Exporter, Invoker, and DubboExporter objects, showing how Dubbo registers services, opens servers, and binds them to Netty transports.