Java-based cross-platform extensible RPC framework design method

Abstract

The invention relates to a java-based cross-platform extensible RPC (Remote Procedure Call) framework design method, which comprises the following steps of: developing a server by java, defining an agent interface class and an entity class, inheriting and realizing the agent interface class by a Controller class, and starting an RPC Server to finish RPC service release; developing a client, and calling an RPC method to be consistent with a local method by starting an RPC Client to be in butt joint with the server; the RPC Server adopts a Netty as a communication framework, starts a TCP (Transmission Control Protocol) service, loads a registered RPC interface class and a registered RPC implementation class at the same time, and registers the RPC Server to a service discovery center; and theRPC Client adopts Netty as a communication framework, loads the registered RPC proxy interface class, is connected with the service discovery center, acquires a subscribed service list and performs connection. According to the invention, the fundamental problem of interconnection among multiple applications can be solved, so that a framework foundation is realized for constructing a target of a distributed service calling network.

Description

technical field [0001] The invention relates to the field of information technology, in particular to a java-based cross-platform scalable RPC framework design method. Background technique [0002] At present, with the continuous development of Internet technology, for an Internet application, with the continuous increase of functional modules, the system will gradually become larger, and it will inevitably be gradually split into multiple applications, and each application will have a relationship. It involves mutual calls, and a single application will deploy multiple sets in order to prevent a single point, so this many-to-many associated call will form a complex distributed service call network. With the increase of calling links, the interconnection mechanism between multiple services has become one of the important basic links of platform construction. At the same time, the commonly used treatment schemes have various limitations. [0003] At present, the following p...

AI Technical Summary

Problems solved by technology

At the same time, the commonly used treatment schemes have various limitations.

[0003] At present, the following problems exist in the prior art for mainly interconnection between java and cross-platform interconnection scenarios: (1) single system problem: with the increase of functional modules, the system becomes larger and larger, even if a single system is adjusted For small functions, it is necessary to re-test and release the entire system, which is not conducive to the stability of the system and increases the difficulty of operation and maintenance

(2) Distributed problem: After the system is split, the interconnection of multiple systems will inevitably form a complex distributed network. If there is no suitable distributed processing strategy, it will cause problems in any link of the distributed network, which will lead to avalanche effect

(3) Performance issues: After the system is split, the interconnection of multiple systems will inevitably form a complex distributed network, and the calls between the systems will be adjusted from local calls to remote calls. If high-performance remote calls cannot be provided, then It is bound to reduce the overall load of the platform

(4) Call cross-platform problem: After RPCServer is released, the client that may be called is a heterogeneous language, and it needs to be able to provide services at this time

(5) Ease of use: In order to meet cross-platform requirements, some commonly used solutions require the use of structured description languages ​​to define interfaces and classes, or add complicated configurations

These all increase the development complexity

(6) Test problem: During client development, there are often test requirements. If the RPCServer is not online at this time, the test cannot be performed

[0004] Although it can realize cross-platform calls when using httpjson to connect, on the one hand, httpjson uses the http protocol, which is lacking in performance

On the other hand, it's cumbersome to call and doesn't work out of the box

When javarmi is used for interconnection, although it is convenient to call between java and have good performance, it is difficult to achieve distribution and cannot be called across platforms

When using webservice to interconnect, although it can be called across platforms, the efficiency is low

When thrift is used for interconnection, although it can be called across platforms, it needs to use a specific structured description language to define interfaces and entities, which is cumbersome

Images