The concepts of HTTP interface, API interface, RPC interface, RMI, WebService, restful, etc.

Before this, we must understand the meaning of the interface, I think in this kind of interface to understand the rules are very appropriate.

HTTP Interface : Development interface based on HTTP protocol. This does not preclude the use of other protocols.

API Interface : API (Application Programming Interface) application programming interface, applications also include Web applications, just like the API documentation is basically the user manual, API interface can be simply understood as " The application uses interfaces.

RPC Interface : remote Procedure Calls A remoting procedure call (RPC) is a protocol that a program can use to request services from a program on another computer in the network. Because programs that use RPC do not have to understand the network protocols that support communication, RPC improves program interoperability. In RPC, the program that makes the request is the client program, and the program that provides the service is the server. RPC (Remote Procedure Call) is a technology that is widely used to support distributed applications (applications where different components are distributed across different computers). The primary purpose of RPC is to provide a way for components to communicate with each other so that they can make requests to each other and pass the results of these requests. No language restrictions.

RMI: RMI (remote method invocation) RMI is for the Java language, RMI allows you to write distributed objects using Java

WebService Interface: WebService is the external interface of the system, such as you want to get resources or information from other websites or servers, others will not share the database to you, he can only provide you with a method they have written to obtain data, you reference the interface he provided can use his written method, so as to achieve the purpose of data sharing.

restful: short REST is a network system that describes an architectural style, the core of which is resource-oriented, and REST is designed and developed for network applications to reduce the complexity of development and improve the scalability of the system. Rest presents design concepts and guidelines for:

1. Everything on the network can be abstracted as a resource (Resource)

2. Each resource has a unique resource identifier (resource identifier), and the operation of the resource does not change these identities

3. All operations are non-stateful

The difference between RPC and RMI, there are a lot of blogs, I will not say. Webservice and restful, I don't know what you're talking about (Webservice This is a big class, including restful) you can look at the SOAP The difference between Webservice and restful Webservice. Do not deliberately confused to find the difference, some from different angles, levels. It is also possible to reconcile one thing with another (at different levels and angles). In today's era of software flooding, different people are called different, and there are many other concepts.

Above is my personal opinion, if there is objection, please correct me. Reproduced in the source.

The concepts of HTTP interface, API interface, RPC interface, RMI, WebService, restful, etc.