Hybrid Architecture Message System and Message Transmission Method Based on Thrift Data Format

Abstract

The present invention relates to a mixed architecture message system and message transmission method based on the Thrift data format, wherein the message system includes: a basic protocol establishment module, used to establish a basic protocol according to the Thrift interface definition language; a TCP connection establishment module, used to establish The TCP connection between the client and the server, and keep this TCP connection as a long connection through the heartbeat message; the message exchange module is used to exchange the message between the client and the server according to the basic protocol; the service implementation module is used to exchange the message according to the described The Thrift interface definition language implements the Thrift service of the server, receives the processing result of the Thrift service from the client, and provides the Thrift service externally through the remote procedure call function. Compared with the prior art, the invention has the advantages of simple structure, low maintenance cost and low risk.

Description

technical field [0001] The invention relates to the technical field of computer networks, in particular to a message system and a message transmission method based on a mixed architecture of Thrift data format. Background technique [0002] Thrift is a remote service call (RPC) framework that supports custom service interfaces and provides remote client calls. By using a language-independent interface definition language IDL (Interface Definition Language), clients in multiple programming languages ​​can be generated end, so that a service can be called by clients of many different languages. Essentially what thrift provides is a system for message interaction between different machines and provides a complete protocol stack. [0003] However, since Thrift is an RPC system, it can only passively provide services for clients to access services. Similar to the HTTP protocol, this is a short-connection service. Every time you call a service, you need to reconnect to call the s...

AI Technical Summary

Problems solved by technology

[0003] However, since Thrift is an RPC system, it can only passively provide services for clients to access services. Similar to the HTTP protocol, this is a short-connection service. Every time you call a service, you need to reconnect to call the service. The server cannot actively send messages to the client. Although a connection can be reused, it still does not have the functions required by the long connection method, and the server can only passively wait for the client to call and reply to the message. When it is necessary to maintain a long connection, And it cannot function in the system environment where the server needs to send messages to the client

The problem can also be solved by implementing the service on the client side, but this method requires the client side to provide external access ports. In some environments, due to security and other restrictions, the access port cannot be opened at will. This method is impossible

[0004] On the other hand, in existing systems that support long-term connections, the protocol used may be a custom data format. In a system that needs to support both scenarios, it is inevitable to do a lot of cumbersome data The conversion between formats will bring some unnecessary performance loss to the system, and also increase the complexity of the system, making the system difficult to maintain

Images