1. Why do you say that to get the microservice architecture, get the RPC framework first?
If there is no unified service framework, RPC framework , the service providers of each team need to implement a set of serialization, deserialization, network framework, connection pool, sending and receiving threads, timeout processing, state machine and other "outside the business". Duplication of technical labor results in overall inefficiency.
Therefore, the unified RPC framework to uniformly handle the above-mentioned "outside the business" technical labor is the primary problem to be solved by service.
The RPC framework enables the caller to "call a remote function (service) as if it were a local function".
2. RPC framework responsibilities
Through the above discussion, the RPC framework needs to shield various complexities from the caller, and also shields various complexities from the service provider :
1) The caller feels like calling a local function
2) The service provider feels like implementing a local function to implement the service
Therefore, the entire RPC framework is divided into the client part and the server part, which are responsible for shielding the complexities of the whole non-(1) (2), and these complexities are the responsibility of the RPC framework.
To be more refined,
The client side also includes: serialization, deserialization, connection pool management, load balancing, failover, queue management, timeout management, asynchronous management, and so on.
The server side includes: server-side components, server-side sending and receiving packet queues, io threads, worker threads, serialization and deserialization, context managers, timeout management, asynchronous callbacks, and so on.
3.