CN118394540A - Novel RPC transmission method based on Java language - Google Patents

Abstract

The invention provides a novel RPC transmission method based on Java language, which comprises the following steps: s1: the service provider reads the configuration file information; s2: scanning HTTP interface class under corresponding service, taking URL as key, instantiation object of class and method as value, storing into service information Map; s3: creating a server socket; s4: creating registration information and uploading the registration information to a registration center; s5: the service consumer reads the configuration file information; s6: reading registry data; s7: scanning an interface of the self-defined RPC annotation, and creating a dynamic proxy; s8: creating request information and sending the request information to a service provider; s9: obtaining request information; s10: finding corresponding code information according to the request information and executing codes; s11: creating response information according to the returned result, packaging the response information into a binary message body, and returning the binary message body to the service consumer; s12: unpacking the message body to obtain the response information.

Description

Novel RPC transmission method based on Java language

Technical Field

The invention relates to the technical field of computers, in particular to a novel RPC transmission method based on Java language.

Background

RPC (Remote Procedure Call) remote procedure call protocol, a protocol that requests services from a remote computer over a network without knowledge of underlying network technology; RPC it assumes the existence of certain protocols, such as TPC/HTTP, etc., to carry information data between communication programs; in the OSI network seven-layer model, the RPC spans a transport layer and an application layer, and makes it easier to develop applications including network distributed multiprogramms;

there are two main classes of RPC frameworks for the current Java language open source: one type is framework software implemented by using HTTP protocol, such as OpenFeign; another class is framework software implemented using the TCP protocol, such as Dubbo;

two types of RPC frames in the prior art have the following defects:

1. The HTTP protocol contains a large amount of useless header information, the data transmission efficiency is low, a large amount of bandwidth is wasted, system resources are occupied, the HTTP protocol is stateless, TCP connection needs to be established for each remote call, the cost is relatively high, the HTTP protocol is an application layer protocol, and compared with a transmission layer TCP protocol, the HTTP protocol is slower and has lower safety;

2. the TCP protocol service provider and the service consumer need to introduce a public interface package, are strongly coupled, cannot call an HTTP interface, are unreadable in messages, and are not friendly to developers.

Disclosure of Invention

The invention aims to solve the defects in the prior art, and provides a novel RPC transmission method based on Java language.

In order to achieve the above purpose, the invention adopts the following technical scheme:

A novel RPC transmission method based on Java language comprises the following steps:

s1: the service provider reads the configuration file information;

Creating a configuration file by a user;

the service provider loads a configuration file into a memory through a configuration file analysis tool, and reads configuration file information;

The configuration file information comprises a registry address, a service name, a port number, a scanning packet path and the like;

the service names are in one-to-one correspondence with the services, and the services comprise HTTP interface classes;

S2: scanning HTTP interface class under corresponding service, taking URL as key, instantiation object of class and method as value, storing into service information Map;

Scanning all HTTP interface classes under the service corresponding to the service name through a Java reflection mechanism according to the read service name, and acquiring an instantiation object and a method of the HTTP interface class;

If the HTTP interface class has the URL annotation of class level, acquiring the URL annotation value of the corresponding class level;

traversing the method contained under the HTTP interface class, and if the traversed method has URL annotation of the method level, acquiring the URL annotation value of the corresponding method level;

Splicing the URL annotation value of the class level and the URL annotation value of the method level to construct a complete URL, namely the constructed complete URL=the URL annotation value of the class level and the URL annotation value of the method level;

Taking the constructed complete URL as a key, and taking an instantiation object and a method of the class as values, and storing the instantiation object and the method into a service information Map;

S3: creating a server socket;

The method comprises the following substeps:

S31: creating a custom TCP protocol;

creating a custom TCP protocol by a user;

s32: creating a server socket;

A user creates a service port socket and monitors a client request of a port number; when a client requests connection, a server socket receives the connection and creates a new socket to process communication with the client, and analyzes data contained in the received request based on the specification of a custom TCP protocol;

s4: creating registration information and uploading the registration information to a registration center;

the service name, the IP address and the port number in the package configuration file information are registration information;

the specific packaging method is as follows:

creating a registration information object, and setting a service name, a port number and an ip address of the registration information object as the corresponding service name, port number and ip address of a server where the service is located in the configuration file information;

According to the registration information address in the read configuration file, the service provider establishes socket connection with the registration center, and the registration information is sent to the registration center through the socket;

s5: the service consumer reads the configuration file information;

the service consumer loads the configuration file into the memory, reads the configuration file information, and obtains a registry address, a load balancing mode and a scanning packet path;

the interface class corresponding to the interface of the custom RPC annotation under the scanning packet path and the annotation on the method contained in the interface class are consistent with the annotation on the HTTP interface class and the method; and the parameters and the return value types of the interface method are consistent with those of the HTTP interface class method, and the method names and the class names are not required to be consistent.

S6: reading registry data;

The service consumer establishes socket connection with the registry according to the registry address, and acquires all registration information from the registry;

the IP address and the port number in the registration information form a corresponding List;

the List of service names, namely keys, IP addresses and port numbers is taken as a value to be stored in the Map;

s7: scanning an interface of the self-defined RPC annotation, and creating a dynamic proxy;

Scanning the interface class corresponding to the interface of the self-defined RPC annotation under the obtained scanning packet path through a Java reflection mechanism, and annotating on the method contained in the interface class;

acquiring a service name corresponding to the custom RPC annotation, and acquiring a value of the service name, namely a List of the IP address and the port number, from the Map according to the service name;

Creating a dynamic proxy implementation class of an RPC annotated interface, wherein the dynamic proxy implementation class selects an IP address and a port number of a service provider from a List according to a load balancing mode, and establishes socket connection with the service provider;

obtaining the annotated values on the interface class and the method through reflection, forming a URL, and packaging parameters of the URL and the method into request information;

Packaging the request information into a binary message body according to a custom TCP protocol rule; when the service consumer code is executed, the method parameters are packaged and the message body is sent to the service provider;

S8: creating request information and sending the request information to a service provider;

the service consumer calls the method of the dynamic proxy implementation class of the interface, creates request information, pack the request information into the binary message body according to the custom agreement;

Establishing socket connection with a service provider, sending a message body to the service provider through the socket, and waiting for response information;

the request information comprises a request ID, a URL and a request parameter;

s9: obtaining request information;

the service provider receives a message body sent by a service consumer through a socket, unpacks the message body according to a self-defined TCP protocol, and obtains request information;

The request information comprises a request ID, a URL and a request parameter;

S10: finding corresponding code information according to the request information and executing codes;

Acquiring a URL according to the request information, and finding out corresponding service information from the service information Map according to the URL;

The method in the service information is executed through a Java reflection mechanism by transmitting request parameters in the request information, and a return result of the method is obtained;

s11: creating response information according to the returned result, packaging the response information into a binary message body, and returning the binary message body to the service consumer;

The format of the response information is as follows: request id+status code+return result+status description;

The state code comprises 0 and 1, if the state code is 0, the execution result of the server is abnormal, and if the state code is 1, the execution result of the server is normal;

the state description is a further description of the state code results;

according to a self-defined protocol, packaging response information into a binary message body, and returning the message body to a service consumer through a socket;

s12: unpacking the message body to obtain response information;

The service consumer receives a message body returned by the service provider through the socket, unpacks the message body into response information according to a self-defined protocol, obtains result data from the response information, and returns the result data.

Compared with the prior art, the invention has the beneficial effects that:

The novel RPC transmission method based on Java language generates service information in a custom format by scanning HTTP interface codes; when registration information is registered in a registration center, the registration information is not registered in the form of a traditional class name and a traditional method name, but in the form of a class annotation value and a method annotation value, so that dependence on a public interface package and weak coupling are eliminated; the code of the HTTP interface is remotely called through the self-defined TCP protocol, so that the advantages of high transmission efficiency, high transmission speed, high safety and low cost are realized, and the message body does not contain code information of a specific language, so that cross-language transmission can be realized; the HTTP interface is readable and testable and is friendly to developers.

Detailed Description

For a further understanding of the objects, construction, features, and functions of the invention, reference should be made to the following detailed description of the preferred embodiments.

A novel RPC transmission method based on Java language comprises the following steps:

s1: the service provider reads the configuration file information;

Creating a configuration file by a user;

the service provider loads a configuration file into a memory through a configuration file analysis tool, and reads configuration file information;

The configuration file information comprises a registry address, a service name, a port number, a scanning packet path and the like;

the service names are in one-to-one correspondence with the services, and the services comprise HTTP interface classes;

S2: scanning HTTP interface class under corresponding service, taking URL as key, instantiation object of class and method as value, storing into service information Map;

Scanning all HTTP interface classes under the service corresponding to the service name through a Java reflection mechanism according to the read service name, and acquiring an instantiation object and a method of the HTTP interface class;

If the HTTP interface class has the URL annotation of class level, acquiring the URL annotation value of the corresponding class level;

traversing the method contained under the HTTP interface class, and if the traversed method has URL annotation of the method level, acquiring the URL annotation value of the corresponding method level;

Splicing the URL annotation value of the class level and the URL annotation value of the method level to construct a complete URL, namely the constructed complete URL=the URL annotation value of the class level and the URL annotation value of the method level;

Taking the constructed complete URL as a key, and taking an instantiation object and a method of the class as values, and storing the instantiation object and the method into a service information Map;

S3: creating a server socket;

The method comprises the following substeps:

S31: creating a custom TCP protocol;

creating a custom TCP protocol by a user;

The custom TCP protocol format is: magic number + version + message category + compression type + serialization type + message length + message body;

the magic number is a special value for identifying the start or the end of the TCP protocol, and the size is 4 bytes;

the version is a version number of the TCP protocol, and the size is 1 byte;

the message category refers to the purpose or meaning of the message, and comprises a request message, a response message and the like, wherein the size of the message is 1 byte;

The compression type is a compression algorithm type specifically adopted by the compressed message, and the size is 1 byte;

the serialization type refers to a method for converting a message into a byte stream, and comprises JSON, XML, protocol Buffers and the like, wherein the size of the message is 1 byte;

the length of the message text with the message length being in bytes is 4 bytes;

The message body refers to an actual response message or a request message;

s32: creating a server socket;

A user creates a service port socket and monitors a client request of a port number; when a client requests connection, a server socket receives the connection and creates a new socket to process communication with the client, and analyzes data contained in the received request based on the specification of a custom TCP protocol;

s4: creating registration information and uploading the registration information to a registration center;

the service name, the IP address and the port number in the package configuration file information are registration information;

the specific packaging method is as follows:

creating a registration information object, and setting a service name, a port number and an ip address of the registration information object as the corresponding service name, port number and ip address of a server where the service is located in the configuration file information;

According to the registration information address in the read configuration file, the service provider establishes socket connection with the registration center, and the registration information is sent to the registration center through the socket;

s5: the service consumer reads the configuration file information;

the service consumer loads the configuration file into the memory, reads the configuration file information, and obtains a registry address, a load balancing mode and a scanning packet path;

the interface class corresponding to the interface of the custom RPC annotation under the scanning packet path and the annotation on the method contained in the interface class are consistent with the annotation on the HTTP interface class and the method; and the parameters and the return value types of the interface method are consistent with those of the HTTP interface class method, and the method names and the class names are not required to be consistent.

S6: reading registry data;

The service consumer establishes socket connection with the registry according to the registry address, and acquires all registration information from the registry;

the IP address and the port number in the registration information form a corresponding List;

the List of service names, namely keys, IP addresses and port numbers is taken as a value to be stored in the Map;

s7: scanning an interface of the self-defined RPC annotation, and creating a dynamic proxy;

Scanning the interface class corresponding to the interface of the self-defined RPC annotation under the obtained scanning packet path through a Java reflection mechanism, and annotating on the method contained in the interface class;

acquiring a service name corresponding to the custom RPC annotation, and acquiring a value of the service name, namely a List of the IP address and the port number, from the Map according to the service name;

Creating a dynamic proxy implementation class of an RPC annotated interface, wherein the dynamic proxy implementation class selects an IP address and a port number of a service provider from a List according to a load balancing mode, and establishes socket connection with the service provider;

obtaining the annotated values on the interface class and the method through reflection, forming a URL, and packaging parameters of the URL and the method into request information;

Packaging the request information into a binary message body according to a custom TCP protocol rule; when the service consumer code is executed, the method parameters are packaged and the message body is sent to the service provider;

S8: creating request information and sending the request information to a service provider;

the service consumer calls the method of the dynamic proxy implementation class of the interface, creates request information, pack the request information into the binary message body according to the custom agreement;

Establishing socket connection with a service provider, sending a message body to the service provider through the socket, and waiting for response information;

the request information comprises a request ID, a URL and a request parameter;

s9: obtaining request information;

the service provider receives a message body sent by a service consumer through a socket, unpacks the message body according to a self-defined TCP protocol, and obtains request information;

The request information comprises a request ID, a URL and a request parameter;

S10: finding corresponding code information according to the request information and executing codes;

Acquiring a URL according to the request information, and finding out corresponding service information from the service information Map according to the URL;

The method in the service information is executed through a Java reflection mechanism by transmitting request parameters in the request information, and a return result of the method is obtained;

s11: creating response information according to the returned result, packaging the response information into a binary message body, and returning the binary message body to the service consumer;

The format of the response information is as follows: request id+status code+return result+status description;

The state code comprises 0 and 1, if the state code is 0, the execution result of the server is abnormal, and if the state code is 1, the execution result of the server is normal;

the state description is a further description of the state code results;

according to a self-defined protocol, packaging response information into a binary message body, and returning the message body to a service consumer through a socket;

s12: unpacking the message body to obtain response information;

The service consumer receives a message body returned by the service provider through the socket, unpacks the message body into response information according to a self-defined protocol, obtains result data from the response information, and returns the result data.

The client calls only by creating a custom interface and an interface method, class annotation and method annotation to be called are added on interface classes and methods, and the parameter entering and returning values of the methods are consistent with the parameter entering and returning values of the methods of the server; the code of the HTTP interface is remotely called through the self-defined TCP protocol, so that the advantages of high transmission efficiency, high transmission speed and high safety are realized, and the message body does not contain code information of a specific language, so that cross-language transmission can be realized. The HTTP interface is readable and testable and is friendly to developers.

The invention has been described with respect to the above-described embodiments, however, the above-described embodiments are merely examples of practicing the invention. It should be noted that the disclosed embodiments do not limit the scope of the invention. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention.

Claims (6)

1. A novel RPC transmission method based on Java language is characterized in that: the method comprises the following steps:

s1: the service provider reads the configuration file information;

Creating a configuration file by a user;

the service provider loads a configuration file into a memory through a configuration file analysis tool, and reads configuration file information;

The configuration file information comprises a registry address, a service name, a port number and a scanning packet path;

the service names are in one-to-one correspondence with the services, and the services comprise HTTP interface classes;

S2: scanning HTTP interface class under corresponding service, taking URL as key, instantiation object of class and method as value, storing into service information Map;

S3: creating a server socket;

The method comprises the following substeps:

S31: creating a custom TCP protocol;

creating a custom TCP protocol by a user;

s32: creating a server socket;

A user creates a service port socket and monitors a client request of a port number; when a client requests connection, a server socket receives the connection and creates a new socket to process communication with the client, and analyzes data contained in the received request based on the specification of a custom TCP protocol;

s4: creating registration information and uploading the registration information to a registration center;

the service name, the IP address and the port number in the package configuration file information are registration information;

According to the registration information address in the read configuration file, the service provider establishes socket connection with the registration center, and the registration information is sent to the registration center through the socket;

s5: the service consumer reads the configuration file information;

the service consumer loads the configuration file into the memory, reads the configuration file information, and obtains a registry address, a load balancing mode and a scanning packet path;

S6: reading registry data;

The service consumer establishes socket connection with the registry according to the registry address, and acquires all registration information from the registry;

s7: scanning an interface of the self-defined RPC annotation, and creating a dynamic proxy;

acquiring a service name corresponding to the custom RPC annotation, and acquiring a value of the service name, namely a List of the IP address and the port number, from the Map according to the service name;

Creating a dynamic proxy implementation class of the RPC annotated interface;

S8: creating request information and sending the request information to a service provider;

the service consumer calls the method of the dynamic proxy implementation class of the interface, creates request information, pack the request information into the binary message body according to the custom agreement;

Establishing socket connection with a service provider, sending a message body to the service provider through the socket, and waiting for response information;

the request information comprises a request ID, a URL and a request parameter;

s9: obtaining request information;

the service provider receives a message body sent by a service consumer through a socket, unpacks the message body according to a self-defined TCP protocol, and obtains request information;

The request information comprises a request ID, a URL and a request parameter;

S10: finding corresponding code information according to the request information and executing codes;

Acquiring a URL according to the request information, and finding out corresponding service information from the service information Map according to the URL;

The method in the service information is executed through a Java reflection mechanism by transmitting request parameters in the request information, and a return result of the method is obtained;

s11: creating response information according to the returned result, packaging the response information into a binary message body, and returning the binary message body to the service consumer;

s12: unpacking the message body to obtain response information;

The service consumer receives a message body returned by the service provider through the socket, unpacks the message body into response information according to a self-defined protocol, obtains result data from the response information, and returns the result data.

2. The novel RPC transmission method based on Java language as claimed in claim 1, wherein:

In step S2, scanning all HTTP interface classes under the service corresponding to the service name through a Java reflection mechanism according to the read service name, and obtaining an instantiation object and a method of the HTTP interface class;

If the HTTP interface class has the URL annotation of class level, acquiring the URL annotation value of the corresponding class level;

traversing the method contained under the HTTP interface class, and if the traversed method has URL annotation of the method level, acquiring the URL annotation value of the corresponding method level;

Splicing the URL annotation value of the class level and the URL annotation value of the method level to construct a complete URL, namely the constructed complete URL=the URL annotation value of the class level and the URL annotation value of the method level;

And storing the built complete URL as a key, and the instantiation object and method of the class as values into the service information Map.

3. The novel RPC transmission method based on Java language as claimed in claim 1, wherein:

In step S5, the interface class corresponding to the interface of the custom RPC annotation under the scan packet path, the annotation on the method included in the interface class is consistent with the annotation on the HTTP interface class and the method, the parameter and the return value type of the interface method are consistent with the parameter and the return value type of the HTTP interface class method, and the method name and the class name do not need to be consistent.

4. The novel RPC transmission method based on Java language as claimed in claim 1, wherein:

In step S6, the IP address and the port number in the registration information form a corresponding List; list with service name key, IP address and port number is stored as value in Map.

5. The novel RPC transmission method based on Java language as claimed in claim 1, wherein:

In step S7, the dynamic proxy implementation class selects an IP address and a port number of a service provider from the List according to a load balancing manner, and establishes socket connection with the service provider;

obtaining the annotated values on the interface class and the method through reflection, forming a URL, and packaging parameters of the URL and the method into request information;

packaging the request information into a binary message body according to a custom TCP protocol rule; when the service consumer code is executed, the method parameters are wrapped and the message body is sent to the service provider.

6. The novel RPC transmission method based on Java language as claimed in claim 1, wherein:

in step S11, the format of the response information is: request id+status code+return result+status description;

The state code comprises 0 and 1, if the state code is 0, the execution result of the server is abnormal, and if the state code is 1, the execution result of the server is normal;

the state description is a further description of the state code results;

according to the self-defined protocol, the response information is packaged into a binary message body, and the message body is returned to the service consumer through the socket.