Dubbo Generic Invocation: Project Practice and Principle Analysis

This article explores Dubbo's generic invocation feature through a real-world project scenario at vivo. The background involves a unified configuration platform that needs to remotely invoke multiple third-party systems (like A/B testing platforms) to determine whether configuration files should be distributed to end devices.

The authors compare two solution approaches: (1) Direct approach that adds separate API calls for each third-party system, resulting in tight coupling; (2) Using Dubbo's generic invocation to abstract a unified remote call dimension, which maintains original logic while reducing system coupling. Solution two was selected for implementation.

The implementation uses Dubbo's GenericService interface, which provides a single $invoke method accepting three parameters: method name, parameter type array, and parameter value array. The code demonstrates creating a ReferenceConfig with generic=true, then invoking remote services without depending on provider interface JARs.

The article then provides an in-depth analysis of Dubbo's internal principles. For service exposure, Dubbo converts service implementations to Invoker objects through proxy factories, then converts Invokers to Exporters via protocols, registering service metadata to registries. For service consumption, Dubbo generates Invokers from remote service instances and creates dynamic proxy references through ProxyFactory.

The key difference between generic and direct invocation lies in the interfaceClass used: direct calls use the actual service interface (e.g., com.alibaba.dubbo.demo.DemoService), while generic calls use GenericService.class. The RpcInvocation objects differ accordingly, with generic calls wrapping the actual method name and parameters inside $invoke calls. This transformation is handled by GenericFilter on the provider side.

Code examples preserved:

public interface GenericService { Object $invoke(String method, String[] parameterTypes, Object[] args) throws GenericException; }

ReferenceConfig<GenericService> referenceConfig = new ReferenceConfig<>(); referenceConfig.setGeneric(Boolean.TRUE.toString());

Object result = genericService.$invoke(method, parameterTypeArray, parameterValueArray);

The article concludes that generic invocation reduces system coupling by eliminating dependencies on third-party JAR packages, requiring only the service interface path, parameter types, and values to make remote calls.