Data exchange method based on data content-oriented cloud message middleware and cloud message middleware system

Abstract

The invention relates to a data exchange method based on data content-oriented cloud message middleware and a cloud message middleware system. The method includes the following steps: 1) deploying nodes based on the cloud message middleware at different management stations, wherein each of the nodes constitutes a message transmission network; 2) deploying a data content-based stream trigger in each node of the message transmission network; and 3) implementing cross-IDC data exchange through the message transmission network, and implementing content-oriented data exchange through the stream trigger. According to the scheme of the invention, the cross-IDC data exchange can be performed efficiently and stably, and meanwhile, the content-based stream trigger is used to perform data subscription, on-demand forwarding of data can be performed according to the data contents, so that consumers can independently determine the flow direction of data and obtain the required data in a fine-grainedway, the quality of network transmission can be improved, and the network burden can be reduced. Various working modes provided by the invention can be stably used and can support different application scenarios.

Description

technical field [0001] The invention belongs to the field of information technology, and in particular relates to a data exchange method and a cloud message middleware system based on data content-oriented cloud message middleware. Background technique [0002] The existing message middleware adopts the publishing / subscribing mode (Pub / Sub). Among enterprise-level products, there are mainly the following types: (1) IBM MQSeries: supports deployment on multiple platforms; provides multiple API interfaces; a topic (Topic) subscriptions can be sent to multiple subscribers; can handle complex communication protocols; provide reliable, once and only once (Exactly-once) delivery for important messages. (2) SonicMQ: supports point-to-point and publish / subscribe modes. The interface compatibility is good, and it can establish connections with other data systems, support load balancing, and build message middleware clusters; provide reliable, once and only once (Exactly-once) delive...

AI Technical Summary

Problems solved by technology

[0005] (1) Does not support efficient cross-IDC (Internet Data Center, Internet Data Center) message exchange: the existing message queue data is centralized, the exchange process does not bring about physical movement and replication of data, and messages produced by producers enter Waiting for consumption in the message queue, producers and consumers exchange data in the "same queue", and the exchange capability in the same data center is very strong, but it cannot be easily applied to the scene of cross-regional message exchange;

[0006] (2) Content-oriented data exchange is not supported: the existing message queue data is named, and data subscription must depend on the topic (Topic) division of the data by the producer. Consumers can only obtain data according to the topic and not according to the content. Consumers are highly coupled to producers in terms of data content, and cannot perform fine-grained data screening. It is easy to cause data redundancy and it is difficult to dynamically expand subscription relationships, which cannot meet complex content-oriented data exchange requirements.

Images