EasyRPC Framework Overview: Architecture, Server Publishing, and Client Invocation

Remote Procedure Call (RPC) allows invoking services on a remote machine as if they were local, and it helps decouple systems; WebService is an example of an HTTP‑based RPC.

EasyRPC addresses several technical challenges: it uses Netty for communication, Spring for service configuration and bean loading, dynamic proxy on the client side for transparent service calls, and Protostuff for message serialization and deserialization.

Server side publishing includes defining a service interface and its implementation, configuring spring-server.xml , loading custom beans via Spring at startup, exporting the Netty server, and registering the service.

Client side invocation involves configuring spring-client.xml , using a proxy to call the remote service, setting a timeout on RpcFuture to avoid hangs, injecting the service bean through ConsumerFactoryBean , starting the client with refer , and handling automatic reconnection by listening to connectFuture.channel().closeFuture .

Protostuff is employed to implement serialization and deserialization utilities, and a TCP handler deals with message framing by prefixing each message with a 4‑byte length field.