Message distribution method and apparatus

Abstract

The present invention discloses a message distribution method and apparatus. The method comprises the steps of: receiving a message created by a message producer, and writing the received message into a message database; obtaining a message subscription range of a message subscriber, and determining an initial message subscription point in the message database according to the message subscription range; starting from the message subscription point, distributing each message in the message subscription range of the message subscriber to the message subscriber. According to the invention, messages obtained by the message subscriber and messages not yet obtained by the message subscriber are determined according to time value and sequence value; the subscribed messages are continuously and complementarily transmitted by the message subscriber; consistency of the subscribed messages is checked; and a message database copy is only used for multiple message subscribers at the same time without using different message data copies for the message subscribers separately; thereby message storage resources are saved.

Description

technical field [0001] The invention relates to the technology in the field of computer communication, in particular to a message distribution method and device. Background technique [0002] JMS, Java Message Service, Java Message Service, is a standard developed by the Java Standardization Organization (JCP) (code-named JSR914), which is an API (Application Programming Interface, Application Programming Interface, application programming interface). JMS is used to send messages between two applications, or in a distributed system, for asynchronous communication. [0003] JMS provides services for creating, sending, receiving, and reading messages. There are two basic message models under the JMS specification, namely PTP (point-to-point) and Pub / Sub (publish / subscribe). Among them, the Pub / Sub model can define multiple consumers to consume messages. It is widely used in enterprise-level development, which facilitates the transmission of messages between systems, saves a ...

AI Technical Summary

Problems solved by technology

In addition, the JMS TOPIC specification does not support message checking. For business scenarios that require high message consistency (such as financial data, order data, etc.), periodic message checking is required, and the existing JMS TOPIC specification does not support the review of historical messages. , so it is impossible to check the consistency of historical messages, and it is also difficult to check when messages are inconsistent

[0011] In addition, although the latter of the above two implementations of the JMS TOPIC specification provides a cache for each subscriber, it is limited by the depth of the cache queue and cannot guarantee that messages will not be lost. Cache, and then store multiple copies of messages at the same time, resulting in a waste of storage resources

Images