Deep Learning Dubbo

1. What is RPC protocol?

The full name of RPC is Remote Procedure call, which is an inter-process communication method. It allows a program to call a procedure or function of another address space (usually on another machine on a shared network) without the programmer explicitly coding the details of this remote invocation. That is, programmers, whether they call local or remote, write essentially the same calling code.

Resources:

In layman's RPC-shallow out-wink-Blog channel-csdn.net

2. Why should I use RPC protocol?

1. Simple: The semantics of RPC concepts are clear and simple, which makes it easier to build distributed computing.

2. Efficient: Process calls look very simple and efficient.

3. General: The process in single-machine computing is often the most important communication mechanism between different algorithm parts.

In layman's terms, it is common for programmers to be familiar with local process calls, so we make RPC as a local call, which is much easier to accept and use without obstacles.

2. What are the common RPC frameworks and what are their characteristics?

3. How is the RPC framework called?

The program that implements RPC generally consists of 5 parts: User, User-stub, Rpcruntime, Server-stub, Server.

Here the user is the client side, when the user wants to initiate a remote call, it is actually called by the local user-stub. The user-stub is responsible for encoding the called interfaces, methods, and parameters through the agreed protocol specification and transmitting to the remote instance through the local Rpcruntime instance. The remote Rpcruntime instance receives the request and hands it to server-stub for decoding and initiates the local call, and the result is returned to the user.

4, how to choose the appropriate RPC framework?

The RPC framework currently available on the market is already a varied and varied. Needs to be carefully selected according to the actual use of the scene, the selection factors to be considered I feel at least include the following points:

1. Performance indicators

2. Whether a cross-language platform is required

3. Intranet open or public network open

4. The quality and community activity of the open source RPC framework itself

1. What is Dubbo?

3, Dubbo and other RPC framework differences, what advantages does it have?

4, Dubbo framework of the overall structure?

5, Dubbo service load Balancing strategy?

6. Dubbo Call failure policy?

Deep Learning Dubbo