What are the php rpc frameworks?

What is the RPC framework?

If RPC can be summarized in one sentence: Remote Procedure Call (Remote Procedure Call)

Then what is remote call?

Usually we call a method in php, such as a function method like this: localAdd(10, 20). The specific implementation of the localAdd method is either defined by the user, or it is a function in the php library. With, that is to say, the code in the localAdd method is implemented locally, it is a local call!

Remote call means: the specific implementation of the called method is not local to the program running, but in some other remote place.

Remote calling principle

For example, A (client) calls the remoteAdd method provided by B (server):

First, establish a connection between A and B TCP connection;

Then A serializes the method name that needs to be called (remoteAdd here) and method parameters (10, 20) into a byte stream and sends it out;

B accepts what A sends The byte stream is then deserialized to obtain the target method name and method parameters, and then the corresponding method call (possibly localAdd) is executed and the result 30 is returned;

A accepts the remote call result and outputs 30.

The RPC framework encapsulates the details I just mentioned and exposes users to simple and friendly API usage.

Benefits of remote calling

Decoupling: When the server needs to modify the method, the client is completely unaware of it and does not need to make any changes; this method It is often used when collaborating across departments and companies, and the provider of the method is usually called: service exposure.

What is the difference between RPC and Socket?

Through the above simple explanation, it seems that RPC and Socket are similar. They all call remote methods and are all in client/server mode. I also wrote an article before: Let’s talk about sockets in detail. What’s the difference between them?

RPC (remote procedure call) uses client/server Mode enables two processes to communicate with each other. Socket is one of the communication methods often used by RPC. RPC is implemented on the basis of Socket, which requires more network and system resources than Socket. In addition to Socket, RPC also has other communication methods, such as http, the operating system's own pipeline and other technologies to implement calls to remote programs. In Microsoft's Windows system, RPC uses named pipes for communication.

What is the difference between RPC and REST?

After understanding RPC, we know that RPC is in client/server mode and calls remote methods. REST is also a set of API calling protocol methods that we are familiar with. It is also based on client/server mode. , calls the remote method, so what is the difference between them?

REST API and RPC both encapsulate functions into interfaces on the server side and expose them for client calls. However, the REST API is based on the HTTP protocol. REST is committed to passing POST/ in the http protocol. GET/PUT/DELETE and other methods and a human-readable URL to provide an http request. RPC does not need to be based on the HTTP protocol

Therefore, if the two back-end languages ​​call each other, using RPC can achieve better performance (eliminating a series of things such as HTTP headers), and it should be easier. configuration. If the front end calls the back end through AJAX, it is better to use the REST API (because you cannot avoid the HTTP hurdle anyway).

What are the popular rpc frameworks in php?

Since PHP is the best language in the world, what are the popular RPC frameworks in PHP?

Let’s list them first: phprpc, yar, thrift, gRPC, swoole, hprose

Because time and energy are limited, it is impossible to learn and use them one by one. Choose a few of the most commonly used ones in the world and use them. Because the principle of RPC is the same, both are Client/Server mode, but the usage of each framework is different.

The above is the detailed content of What are the php rpc frameworks?. For more information, please follow other related articles on the PHP Chinese website!