WO2013078689A1 - Method and device for realizing message transfer in cloud message service - Google Patents

Abstract

Provided are a method and device for realizing message transfer in a cloud message service. The method includes: receiving a message sent by a first distributed program, storing the message data carried in the message in a distributed Key-Value storage system, and increasing the message sending sequence number of a message queue corresponding to the message; receiving a request of a second distributed program for reading message data, reading the message data from the distributed Key-Value storage system, sending the read message data to the second distributed program, and increasing the message receiving sequence number of the message queue when the message data is message data corresponding to the receiving sequence number of the message queue. In the embodiments of the present invention, by way of setting a message sending sequence number and a message receiving sequence number for a message queue, when a first distributed program sends message data, a cloud message service device stores the received message data in a distributed Key-Value storage system according to the message sending sequence number of the message queue, and modifies the message sending sequence number incrementally; and when a second distributed program requests to receive message data, the cloud message service device reads the message data according to the message receiving sequence number of the message queue and modifies the message receiving sequence number incrementally. Thus, the high availability and flexibility requirements of the cloud message service are realized, and at the same time the sequence of message transfer is ensured.

Description

 Method and device for realizing message delivery in cloud message service

 Embodiments of the present invention relate to the field of IT technology and, more particularly, to a method and apparatus for implementing message delivery in a cloud messaging service. Background technique

 Distributed programs run on distributed modules to accomplish a task through the network to implement distributed application services. MOM (Mes sage-oriented Middleware) is generally used for communication between distributed programs. MOM provides an effective communication method between distributed programs by providing a message queue model, which provides a distributed system. A loosely coupled way. In a distributed system based on message middleware, communication between distributed programs, through the message middleware system to route and distribute messages, there is no need to establish a direct connection between distributed programs, but through distributed programs and messages A system to establish a connection to achieve communication between distributed programs. A distributed module is a specific physical entity running a distributed program. The distributed application is executed by a distributed program running on multiple modules. The distributed module is connected to a message middleware system running the message middleware to implement distributed Messaging between programs.

 With the development of technologies such as cloud computing and mobile Internet, various types of servers, PCs, and mobile devices deployed in the data center constitute a complex global-scale distributed system. Cloud messaging services use message middleware for this distributed The system provides services for communication.

 The cloud messaging service should first implement high availability and scalability of the message middleware, ensure uninterrupted service capability for a large number of users, and dynamically adjust resources according to load changes. Secondly, provide message delivery while ensuring the former. Order guarantee.

A common way to achieve high availability and scalability in cloud messaging services is to use a distributed Key-Va lue (key-value pair) storage system to store data, but this approach does not provide a sequence guarantee: Implementing cloud messaging services Each message in the cloud message service device has multiple copies stored on multiple servers. When the distributed program receives the message from the cloud message service device, the cloud message service device generally selects a part of the server based on a weighted random selection algorithm. Get the message, if the distributed program continues to request the cloud message service device to receive the message, then according to the selection algorithm will eventually traverse all the servers, all messages will be returned to the distributed program, but because each request is selected to select a part of the server to obtain Messages, there is no guarantee that the order of receiving messages and sending messages The order is the same. However, many programs have requirements for order guarantees, and cloud message services that cannot provide effective order guarantee have application limitations.

 As mentioned above, the current message middleware system can not achieve the high availability and scalability requirements of the cloud message service, and can provide a good sequence guarantee, thus causing the limitation of the cloud message service in application. . Summary of the invention

 The embodiment of the invention provides a method and a device for implementing message delivery in a cloud information service, which can provide a good sequence guarantee while ensuring the high availability and scalability requirements of the cloud message service.

 In one aspect, a method for implementing message delivery in a cloud message service is provided, including: receiving a message sent by a first distributed program, storing message data carried by the message in a distributed Key-Va lue storage system, and incrementing the Sending a message sequence number of the message queue corresponding to the message; receiving a request for reading the message data by the second distributed program, reading the message data in the distributed Key-Va lue storage system, and transmitting the read message data to the second a distributed program, and when the message data is the message data corresponding to the received message sequence number of the message queue, incrementing the received message sequence of the message queue, on the other hand, provides a cloud message service device, including: an interface unit, Receiving a message sent by the first distributed program; receiving a request for the second distributed program to read the message data, and transmitting the message data read by the storage unit to the second distributed program; the message queue management unit, Notifying the storage unit to store the message data carried by the message received by the interface unit, and incrementing the cancellation Sending a message sequence number of the message queue corresponding to the message; in response to the request for reading the message data received by the interface unit, notifying the storage unit to read the message data, and reading the sequence number of the received message of the message queue When the message data is successful, the received message sequence number of the message queue is incremented. The storage unit includes a distributed Key-Va lue storage system for performing storage or reading of the message data.

In the embodiment of the present invention, by setting a sending message sequence number and a receiving message sequence number for each message queue, when the first distributed program sends the message data, the cloud message service device receives the data and generates a sequence number including the sending message queue sending message. The key value Key, using the message data as the value Va lue, storing the message data in the distributed Key-Va lue storage system, and incrementally modifying the sent message sequence number of the message queue; when the second distributed program requests to receive the message data, Cloud messaging service The device reads the message data in the distributed Key-Va lue storage system according to the received message sequence number of the message queue, and incrementally modifies the received message sequence number of the message queue. The high availability and scalability requirements of cloud messaging services are realized, while ensuring the order guarantee of message delivery. DRAWINGS

 In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments will be described in detail below. It is obvious that the drawings in the following description are only some embodiments of the present invention. Other drawings may also be obtained from those of ordinary skill in the art in view of the drawings.

 FIG. 1 is a system architecture diagram of implementing a cloud message service in a distributed system according to an embodiment of the present invention. 2 is a schematic structural diagram of metadata of a message queue in an embodiment of the present invention.

 Figure 3 is a diagram showing the storage format of message data in a Key-Va lue storage system in an embodiment of the present invention.

 4 is a diagram of a method of implementing messaging in a cloud messaging service in accordance with one embodiment of the present invention. Figure 5 is a diagram of a method for providing sequence assurance by distributed program selection messaging in a cloud messaging service in accordance with another embodiment of the present invention.

 6 is a block diagram of a cloud messaging service device in accordance with one embodiment of the present invention. detailed description

 The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without making creative labor are within the scope of the present invention.

 First, the order guarantee is described in the order. The order guarantee means that the distributed program should receive the messages in the same order as the sent messages, and the order of sending the messages cannot be out of order. For example, the order in which the distributed program sends 4 messages is: Message A - Message B - Message C - Message D, then the order in which the distributed program receives these 4 messages should also be: Message A - Message B - Message C - Message D, but not in other order, most distributed programs Requirements can provide order guarantees.

 FIG. 1 is a system architecture diagram of implementing a cloud message service in a distributed system according to an embodiment of the present invention. The embodiments of the present invention described below are applicable to the cloud messaging service system architecture shown in FIG.

As shown in Figure 1, the distributed program sends message data to the cloud message service device or from the cloud message service. The message data is obtained in the service device, thereby realizing message delivery between distributed programs. Distributed programs run on distributed modules. Message passing between distributed programs is actually delivered through message passing between distributed modules. Message passing between distributed programs running on the same distributed module is also passed. Cloud messaging service device. The cloud message service device is mainly divided into three parts: a message queue management unit that performs maintenance management on the message queue, a message delivery, a storage unit that implements message-related data storage, and an interface unit that interfaces with the distributed program.

 As shown in FIG. 2, in the embodiment of the present invention, a message sequence number and a received message sequence number are set for each message queue as metadata of the message queue. Of course, depending on the application, each message queue may also set one or more other metadata such as whether to save order, unread successful message sequence number, message queue length, and so on. Both the send message sequence number and the receive message sequence number are sequences that start from the initial state. The initial state of the two should be the same, such as increasing from 0, or increasing from 1. Each time a distributed program sends a message to the message queue, the sequence number of the sent message of the message queue is incremented by one. Each time the distributed program receives a message from a message queue, the sequence number of the received message of the message queue is incremented by one. . Define the maximum value of a message serial number. When the sending message sequence number exceeds the maximum value of the message sequence number, the sending message sequence number is reversed, that is, it starts counting again from the initial state, for example, 0. Similarly, the received message sequence number exceeds the message. The serial number will also be forwarded when the serial number is the maximum. When the received message sequence number of a message queue is smaller than the sent message sequence number, or the received message sequence number is greater than the sent message sequence number but the sent message queue number is more inverted than the received message sequence number, it indicates that the message queue still exists. A message that is not received by the distributed program, the distributed program can receive the message from the message queue. When the received message sequence number is equal to the sent message sequence number, indicating that the message in the message queue has been received, the message queue will not be received from the message queue. Read messages to distributed programs. Generally, the maximum value of the message sequence number is set to be large enough to avoid the reversed transmission message sequence number receiving the message data and incrementing, and finally exceeds the received message sequence number that is inverted less frequently, resulting in the unread message data being overwritten. Happening.

As shown in FIG. 3, when the message data is stored in the distributed Key-Va lue storage system, the information is composed of the message sequence number, and the specific composition rule includes at least the message queue identifier and the message sequence number, such as Key. The composition may be a message queue identifier + a message sequence number, or a message sequence number + a message queue identifier, and may add other information as a prefix or suffix of the Key, such as a message length, as needed. The message data carried in the received distributed program message is used as Va lue. The message sent by the distributed program received by the cloud message service device generally carries the message queue name, message data, and sometimes also includes a timestamp, a digital signature, and the like. Information, embodiment of the invention Only the part of the message data is saved. Of course, other information carried by the message can also be saved according to the actual application of the message transmission. Therefore, the storage and access of the message data in the distributed Key-Va lue storage system is realized, and the message data in the distributed storage system is directly located and located through the Key containing the message sequence number.

 When the distributed program sends a message, the cloud message service device modifies the sequence number of the message sent by the message queue, and generates a key according to the rule by using the sequence number of the message as the message sequence number, according to the generated key in the distributed Key-Va lue storage system. Store the message data. When the distributed program needs to receive the message, the cloud message service device generates the key according to the rule by using the received message sequence number of the message queue as the message sequence number, and reads the message data according to the generated Key to the distributed Key-Va lue storage system, thereby The order guarantee of message delivery is realized.

 In addition, the program delivers messages through message middleware, often with distribution assurance requirements. There are three general models for distribution assurance: up to one distribution, at least one distribution, and strict one-time distribution. A maximum of one distribution means: For each message, the distributed program that requests the message middleware to receive the message will only receive it at most once, but may not receive it. At least one distribution means: For each message, the distributed program that requests the message middleware to receive the message must be received, but there may be repeated reception. Strict one-time distribution means: For each message, the distributed program that requests the message middleware to receive the message must be received and will only be received once. In general, most applications expect a guarantee of strict one-time distribution.

The usual way to achieve high availability and scalability in cloud messaging services is to use distributed Key-Va lue storage systems for storage of message data, but this method does not provide distribution guarantees: Every message data in the cloud messaging service device has Multiple copies are stored on multiple servers. When the distributed program receives the message data from the cloud message service device, the cloud message service device generally selects a part of the server to obtain the message data based on the weighted random selection algorithm, and the distributed program continues to The cloud message service device requests to receive the message data, then it will eventually traverse all the servers, and all the message data will be returned to the program. If a distributed program requests to receive the message data, a server that stores the received message data copy fails. Then, the status of the message data on the faulty server does not become received or deleted. After the next request to receive the message data, after the server recovers from the fault state, the message data is repeatedly received, that is, Duplicate message appears, only Can guarantee at least one distribution. However, many applications have requirements for distribution assurance, and cloud messaging services that do not provide strict one-time distribution guarantee have application limitations. In summary, the current messaging middleware system cannot meet the high availability and scalability of cloud messaging services. Seeking, can provide a good order guarantee, and further provide the ability to distribute guarantees, thus causing the limitations of cloud messaging services.

 Each message queue is set with at least a message queue identifier, a message sequence number, and a message sequence number. The metadata of the message queue can be stored in a relational database, and the metadata operation is guaranteed by the characteristics of the relational database. Transactional, that is, when multiple programs or multiple server nodes in the cloud message service need to update the metadata of one message queue at the same time, all operations will be treated as a single operation, either successfully completed or not executed at all, no There will be a part of successful failures, and there will be no repeated metadata operations. The message data will be read according to the sequence of sending messages and receiving message sequence numbers of the message queue that does not operate repeatedly. Duplicate messages appear, resulting in a strict distribution guarantee capability.

 In the embodiment of the present invention, when the first distributed program sends the message data, the cloud message service device receives the message data according to the message sequence number of the message queue in the distributed Key-Va lue storage system. Storing the message data, and incrementally modifying the sent message sequence number; when the second distributed program requests to receive the message data, the cloud message service device reads the message data according to the received message sequence number of the message queue, and incrementally modifies the received message sequence number, The order guarantee of the message delivery of the cloud message service is realized. Therefore, the high availability and scalability requirements of the cloud message service are met, and the order guarantee of the message is realized.

 And further, the strict distribution guarantee capability can be realized by storing the metadata of the message queue including the message queue identifier, the sending message sequence number, and the received message sequence number in the relational database. This satisfies the high availability and scalability requirements of the cloud messaging service, while ensuring the order guarantee and distribution guarantee of the message.

 FIG. 4 is a diagram of a method for implementing message delivery in a cloud message service according to an embodiment of the present invention.

 401. Receive a message sent by the first distributed program, store the message data carried by the received message in the distributed Key-Va lue storage system, and increment the sending message sequence number of the message queue corresponding to the message.

The message sent by the first distributed program may be received by using the following method: the message carries a message queue identifier containing a message queue that needs to deliver the message data, and generates a key value Key containing the message sequence number by using the sequence number of the message sequence of the message queue. The key value Key must include at least the message queue identifier and the message sequence number. The specific format may be the message queue identifier + the message sequence number, or the message sequence number + message queue identifier, and other information may be added according to the service requirement, such as the message length. Wait. Thus storing the received message in the distributed Key-Va lue storage system according to the generated Key Message data, and increment the sequence number of the sent message of the message queue by one.

 402. Receive a request for the second distributed program to read the message data, read the message data in the distributed Key-Va lue storage system, and send the read message data to the second distributed program, where the message data is When the message queue receives the message data corresponding to the sequence number of the message, the sequence number of the received message of the message queue is incremented.

 If the message data reading mode is the message data corresponding to the received message sequence number of the message queue, the received message sequence number of the message queue needs to be incremented.

 The method for reading the message data by the second distributed program may be received by the method, where the request includes a message queue identifier for reading the message data, and when the received message sequence number of the message queue is not equal to the serial number of the sent message, the receiving The message sequence number generates a key value Key. Of course, the format of the generated Key here should be consistent with the generated key value Key when receiving the message data, and the message data is read in the distributed Key-Va ue storage system according to the generated Key. If the reading is successful, the read message data is delivered to the second distributed program, and the received message sequence number of the message queue is incremented by one. When the received message sequence number of the message queue is equal to the transmitted message sequence number, the message data is not read. The second distributed program reads the message data request and may also apply to read multiple pieces of message data at a time. The implementation method at this time is similar to the above, except that the operation of reading the message data and modifying the received message sequence number multiple times is repeated.

 Of course, both the message sequence number and the received message sequence number of the message queue define a maximum value. If the message sequence number exceeds the defined maximum value, the message sequence number is inverted, that is, counting from the initial value. For example, the maximum value of the message sequence number is defined as 255, and the initial value is 0. When the message sequence number is 255, a message is received, and the message sequence number of the message queue is changed to 0. In the above steps 401 and 402, when the message sequence number is incremented, if the maximum value of the message sequence number is reached, the message sequence number is inverted.

In this embodiment, the metadata of the message queue is preferably stored in the relational database, and the strict delivery guarantee capability of the message delivery is realized. The message queue identifier can also be used as the key value Key, and the metadata is stored as Va lue in the distributed Key-Va lue storage system. Accordingly, steps 401, 402 read or modify metadata in a relational database or a distributed Key-Va lue storage system. The foregoing metadata includes at least a message queue identifier, a sent message sequence number, and a received message sequence number. In the embodiment of the present invention, when the first distributed program sends the message data, the cloud message service device distributes the message sequence number according to the message queue. Key-Va 1 ue storage system stores messages, and Incrementally modifying the sending message sequence number of the message queue; when the second distributed program requests to receive the message data, the cloud message serving device reads the message data according to the received message sequence number of the message queue, and incrementally modifies the received message sequence number of the message queue, The order guarantee of the message delivery of the cloud message service is realized. Furthermore, by storing and modifying the metadata of the message queue in the relational database, a strict one-time distribution guarantee capability is provided, thereby ensuring the order guarantee of the message delivery and the strict one-time distribution guarantee.

 FIG. 5 is a diagram of a method for selecting whether a message delivery order guarantee is required by a distributed program in a cloud message service according to another embodiment of the present invention. In FIG. 5, when the read message data is unsuccessful, the distributed program selects whether the message delivery sequence guarantee is required to determine the read order of the message data, and the embodiment is based on the embodiment shown in FIG. Step 402 is refined, and the step of receiving the first distributed program to transmit the message data is substantially the same as the method of the step 401 in the embodiment shown in FIG. 4, and thus the illustration of the step of receiving the first distributed program to send the message data is omitted. And description.

 501. Receive a request for the second distributed program to read the message data, and read the message in the distributed Key-Va lue storage system.

 The method for reading the message data by the second distributed program may be received by the method that the message queue identifier of the read message data is included in the request, and when the sequence number of the received message of the message queue is not equal to the serial number of the sent message, receiving The message sequence number generates a key value Key, and the format of the generated Key should be the same as the format of the Key generated when receiving the message data, and the message data is read in the distributed Key-Va lue storage system according to the generated Key. When the received message sequence number of the message queue is equal to the sent message sequence number, the message data is not read.

 In step 502, 501, whether the message data is successfully read in the distributed Key-Va lue storage system is successful.

 When a failure occurs in one or more storage system nodes that store message data, the cloud message service device may not be able to read the message data.

 503. If the reading of the message data in step 502 is unsuccessful, further determining whether the message delivery of the second distributed program requires sequential guarantee.

Whether the second distributed program needs the order of message delivery can be judged according to the value of the metadata "whether or not" of the message queue. If the value is yes, it indicates that order guarantee is needed, otherwise it means that order guarantee is not needed. Further, the value of "whether or not the order" of the message queue can be set by the distributed program through a command message, where the distributed program can be the message data sent in the message delivery. The first distributed program can also be a second distributed program that receives the message data. For example, the first distributed program sends a command message containing a parameter requiring a sequence indication, and sets the value of "whether or not" of the message queue to YES. It is also possible to provide a value of the parameter setting message queue "whether or not" in the request of the second distributed program to read the message data or in the message of the first distributed program to send the message data, for example in the second distributed program read The message data request contains a parameter indicating that order preservation is required, and the value of the message queue "sort order" is set to YES.

 In addition, the order guarantee for determining whether the second distributed program needs to be delivered may also be based on the parameter indicating whether the order is included in the request for reading the message data by the second distributed program, and when the order is instructed, the order guarantee is required. Indication of non-preservation indicates that no order guarantee is required.

 If it is determined that the second distributed program messaging needs to provide a sequence guarantee, the current message data reading process ends and the received message sequence number is not modified. In this way, when the next message data reading process is performed, the unread message data is continuously read according to the received message sequence number until the message data is successfully read, thereby achieving order guarantee.

 504. If it is determined in step 503 that the second distributed program messaging does not need to provide a sequence guarantee, record the unsuccessful message sequence number and read the message data of the next received message sequence number.

 Specifically, the message sequence number of the unread success message is added to the unread success message sequence number of the message queue, and the received message sequence number of the message queue is incremented, and the message data of the next received message sequence number is read. Until the read message data is successful or no message data is readable in the message queue, that is, the received message sequence number of the message queue is equal to the sent message sequence number.

 505. Return the read message data to the second distributed program, and modify the received message sequence number of the message queue.

 Specifically, the message data that is successfully read is returned to the second distributed program, and the sequence number of the received message sequence of the message queue is modified to be 1 and the sequence number of the message is successfully read.

 In the normal message data reading mode, the message data corresponding to the received message sequence number of the message queue is read. At this time, the received message sequence number of the message queue needs to be incremented, that is, the received message sequence number of the message queue is Read the successful message sequence number plus one.

 Similarly, the received message sequence number of the message queue defines a maximum value. If the received message sequence number exceeds the defined maximum value, the message sequence number is inverted, that is, counting again from the initial value.

In the embodiment of the present invention, further, the second distributed program read is received in step 501. The request for the message data first determines whether there is unread message data in the message queue that was originally skipped by the unsuccessful read, and if so, reads the message data. The specific implementation manner may be: determining whether the metadata of the message queue "unread success message sequence number" is empty, and if there is message data that is not successfully read, obtaining a message sequence number from the unread success message sequence number Using the message sequence number to generate a key value Key, reading the message data in the distributed Key-Va lue storage system according to the generated Key, and if the reading is successful, transmitting the read message data to the second distributed program. And the message sequence number that has been read this time is deleted in the unread success message sequence number of the message queue, and the current message data reading process ends. If the reading is unsuccessful, continue to obtain the next message serial number from the unread successful message sequence number until the read message data is successful or not read. The message sequence number is no new message sequence number can be read. take. If the unread success message sequence number of the message queue is empty or the message data corresponding to all the message sequence numbers in the unsuccessful message sequence number is unsuccessfully read, the message is read according to the normal message data reading manner. The queue receives the message data corresponding to the message sequence number.

 The second distributed program reads the message data request and may also apply to read the plurality of message data at a time. The implementation method at this time is similar to the above, except that the operation of reading the message data multiple times and modifying the serial number of the received message is repeated.

 In the embodiment of the present invention, the key value Key includes at least a message queue identifier and a message sequence number, and the specific format may be a message queue identifier + a message sequence number, or a message sequence number + a message queue identifier, and other information may be added according to service requirements. For example, the message length and the like, the format of the key value Key generated when the message data sent by the first distributed module is stored in the distributed Key-Va lue storage system and the message data is read to the second distributed program should be the same.

 In this embodiment, the metadata of the message queue is preferably stored in the relational database, or the message queue identifier is used as the key value Key, and the metadata is stored as Va lue in the distributed Key-Va lue storage system. Accordingly, metadata is read or modified in a relational database or a distributed Key-Va lue storage system. The above metadata includes at least information such as a message queue identifier, a sent message sequence number, a received message sequence number, a hold order, an unread success message sequence number, and the like.

In the embodiment of the present invention, when the first distributed program sends the message data, the message data is stored in the distributed Key-Va lue storage system, and the sequence number of the sent message of the message queue is incrementally modified; when the second distributed program requests the message data Read the message data according to the received message sequence number of the message queue. When the message data fails to be read, determine whether to continue reading the message data until the read is successful, or incrementally modify the message queue according to whether the distributed program needs the order guarantee setting. Receiving message The serial number continues to read the message data of the next received message sequence number, and simultaneously records the message sequence number that has not been successfully read, and then reads it when the subsequent second distributed program requests to read the message data. Thereby, it is determined whether the cloud message service is required to provide strict order guarantee according to the settings of the distributed program. Further, by storing and modifying the metadata of the message queue in the relational database, a strict one-time distribution guarantee capability is provided, thereby ensuring the order guarantee and distribution guarantee of the message delivery.

 6 is a block diagram of a cloud messaging service device in accordance with one embodiment of the present invention. The cloud messaging service device of Figure 6 includes an interface unit 601, a message queue management unit 602, and a storage unit 603.

 The interface unit 601 is configured to receive a message sent by the first distributed program, receive a request for reading the message data by the second distributed program, and send the message data read by the storage unit 603 to the second distributed program. The message queue management unit 602 is configured to notify the storage unit 603 to store the message data carried by the message received by the interface unit 601, and increment the sending message sequence number of the message queue corresponding to the message; the request for reading the message data according to the interface unit 601 The notification storage unit 603 reads the message data, and increments the received message sequence number of the message queue when the message data corresponding to the received message sequence number of the message queue is successfully read. The storage unit 603 includes a distributed Key-Va lue storage system for performing storage or reading of the message data.

 The method may be as follows, the interface unit receives the message sent by the first distributed program, where the message includes a message queue identifier of the message queue that needs to deliver the message data, and the message queue management unit generates the message including the message sequence number of the message queue. The key value of the serial number Key. The message queue management unit notifies the storage unit to store the message data carried in the received message in the distributed Key-Va lue storage system according to the key value Key, and the message queue management unit increments the sequence number of the sent message of the message queue by one.

 The interface unit receives a request from the second distributed program to read the message data, and the request includes a message queue identifier for reading the message data. When the received message sequence number of the message queue is not equal to the sent message sequence number, the message queue management unit generates a key value Key by receiving the message sequence number, and notifies the storage unit to read the message data in the distributed Key-Va lue storage system. If the reading is successful, the interface unit passes the read message data to the second distributed program, and the message queue management unit increments the received message sequence number of the message queue by one.

Further, if the storage unit reads the message data unsuccessfully, the message queue management unit determines whether the message delivery of the second distributed program requires sequential guarantee. If a sequence guarantee is required, the message queue management unit notifies the storage unit to continue reading the unread message data until Successfully read the message data. If the second distributed program message delivery does not need to provide a sequence guarantee, the message queue management unit records the message sequence number of the unsuccessful read, and increments the received message sequence number of the message queue, and notifies the storage unit to read the next received message sequence number. Message data. The specific method may be that the message queue management unit adds the message sequence number of the unread success message to the unread success message sequence number of the message queue, and reads the message data of the next received message sequence number until the message is read. The message data is successful or no message data is readable in the message queue, that is, the received message sequence number of the message queue is equal to the sent message sequence number.

 The above-mentioned message queue management unit determines whether the order of the second distributed program needs to be delivered can be determined according to the value of the metadata of the message queue "whether or not the order is saved", and if the value is yes, it indicates that order guarantee is required, otherwise it means that it is unnecessary. Order guarantee. Further, whether the value of the message queue is saved may be set by the message queue management unit according to the command message of the distributed program, and the distributed program may be the first distributed program that sends the message data in the message delivery or the received message data. The second distributed program. For example, the first distributed program sends a command message containing parameters requiring a sequence indication, and the message queue management unit sets the value of the message queue's order to be YES. The message queue management module may also be configured according to the request of the second distributed program to read the message data or the parameter carried by the message of the first distributed program to send the message data, for example, in the request of the second distributed program to read the message data. The inclusion of a parameter indicates that the message delivery needs to be preserved, and the message queue management unit sets the value of the message queue to be guaranteed to be YES. In addition, the message queue management unit determines whether the second distributed program needs the order of message delivery, and may also include a parameter indicating whether to save the order included in the request for reading the message data by the second distributed program, and indicates Order guarantee is required, indicating no order preservation means no order guarantee is required.

In the embodiment of the present invention, the receiving unit further receives a request for the second distributed program to read the message data, and the message queue management unit first determines whether the message queue has an unread original that was not successfully read. The message data can be determined by determining whether the metadata of the message queue "unread successful message sequence number" is empty. If there is unread successful message data, the storage unit is notified to read the message data. In a specific implementation manner, the message queue management unit obtains a message sequence number from the unread success message sequence number, and generates a key value Key by using the message sequence number to notify the storage unit to read in the distributed Key-Va lue storage system. Taking the message data, if the reading is successful, the interface unit transmits the read message data to the second distributed program, and the message queue management unit deletes the read in the unread successful message sequence number of the message queue. Take the successful message sequence number. If the read is unsuccessful, the message queue management unit continues to successfully cancel from the unquery of the message queue. The next message sequence number is obtained in the sequence number until the message data is successfully read or not read. The message sequence is read in the sequence number of the message. If the unread success message sequence number of the message queue is empty or the message data corresponding to all message sequence numbers in the unsuccessful success message sequence number is unsuccessfully read, the message queue management unit notifies the storage unit to obtain the message queue reception. The message data corresponding to the message sequence number. In the embodiment of the present invention, the key value Key includes at least a message queue identifier and a message sequence number, and the specific format may be a message queue identifier + a message sequence number, or a message sequence number + a message queue identifier, and other information may be added according to service requirements. For example, the message length and the like, the format of the key value Key generated when the message data sent by the first distributed module is stored in the distributed Key-Va lue storage system and the message data is read to the second distributed program should be the same. The key value Key can be generated by the message queue management unit, and then the storage unit is notified to store or read the message data in the distributed Key-Va lue storage system according to the Key. The message queue management unit may also only transmit information such as a message queue identifier, a message sequence number, and the like of the message queue to the storage unit, and the storage unit generates a key value Key to store or read the message data in the distributed Key-Va lue storage system.

 Certainly, in this embodiment, the message sequence number and the received message sequence number of the message queue both define a maximum value, and if the message sequence number exceeds the defined maximum value, the message sequence number is reversed, that is, the number is restarted from the initial value. . When the message queue management unit increments the message sequence number, if the maximum value of the message sequence number is reached, the message sequence number is reversed.

 In this embodiment, the storage unit may further include a relational database, and preferably store the metadata of the message queue in the relational database, or use the message queue identifier as the key value Key, and the metadata is stored as Va lue in the distribution. In the Key-Va lue storage system. The storage unit also reads or modifies the metadata of the message queue in a relational database or distributed Key-Va lue storage system. The above metadata includes at least one of a message queue identifier, a sent message sequence number, a received message sequence number, a hold order, an unread success message sequence number, and the like.

 The distributed Key-Va lue storage system and the relational database in this embodiment, as part of the storage unit, may be physically together with other parts of the cloud message service device, or may be distributed on multiple network physical entities. .

Therefore, when the first distributed program sends a message, the cloud message service device of the embodiment of the present invention stores the message data carried by the message in the distributed Key-Va lue storage system, and incrementally modifies the sequence of the message sequence of the message queue; When the second distributed program requests to receive the message data, according to the cancellation The received message sequence number of the message queue reads the message data, and incrementally modifies the received message sequence number of the message queue, thereby realizing the sequence guarantee of the message delivery of the cloud message service. And further, when the reading of the message data fails, determining whether to continue reading the message data until the reading is successful according to whether the distributed program needs the order guarantee requirement, or continuing to read the message data of the next received message sequence number, and simultaneously The sequence number of the message that has not been successfully read is recorded, and is read after the subsequent distributed program requests to read the message data, thereby realizing whether the cloud message service is required to provide strict order guarantee according to the setting of the distributed program. Further, by storing and modifying the metadata of the message queue in the relational database, a strict one-time distribution guarantee capability is provided, thereby ensuring the order guarantee and distribution guarantee of the message delivery.

 Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software or a combination of both, in order to clearly illustrate hardware and software. Interchangeability, the composition and steps of the various examples have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

 It will be apparent to those skilled in the art that, for the convenience of the description and the cleaning process, the specific operation of the system, the device and the unit described above may be referred to the corresponding processes in the foregoing method embodiments, and details are not described herein again.

 In the several embodiments provided herein, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not executed. In addition, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical, mechanical or otherwise. The components displayed for the unit may or may not be physical units, ie may be located in one place, or may be distributed over multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solution of the embodiment.

In addition, each functional unit in various embodiments of the present invention may be integrated into one processing unit In addition, each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

 The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may contribute to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM, Random Acces s Memory), a magnetic disk or an optical disk, and the like, which can store program codes. medium.

 The above is only the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the claims.

Claims

Rights request  A method for implementing message delivery in a cloud message service, comprising: receiving a message sent by a first distributed program, storing the message data carried by the message in a distributed Key-Va lue storage system, and Incrementing the sequence of sent messages of the message queue corresponding to the message -  Receiving a request for the second distributed program to read the message data, reading the message data in the distributed Key-Va lue storage system, and transmitting the read message data to the second distributed program, And when the message data is the message data corresponding to the received message sequence number of the message queue, incrementing the received message sequence number of the message queue.  The method of claim 1, wherein the storing the message data carried by the message in the distributed Key-Va lue storage system comprises: generating a key value Key including the serial number of the sent message And storing the message data carried by the message in the distributed Key-Va lue storage system according to the key value Key.  The method of any one of claims 1-2, wherein the reading the message data in the distributed Key-Va lue storage system comprises: generating a serial number including the received message The key value Key is read in the distributed Key-Va lue storage system according to the key value Key.  The method according to any one of claims 1-3, wherein the transmission message sequence number and the received message sequence number are stored in a relational database.  The method according to any one of claims 1-4, wherein the message sequence number of the message queue and the initial value of the received message sequence number are the same.  The method according to any one of claims 1-5, wherein when the sequence number of the message sequence of the message queue is incremented, if the sequence number of the message sequence exceeds the maximum value of the message sequence number, Said to send the message serial number to the initial value; or  When the received message sequence number of the message queue is incremented, if the received message sequence number exceeds the maximum value of the message sequence number, the received message sequence number is reset to an initial value.  The method according to any one of claims 1 to 6, wherein if the received message sequence number of the message queue corresponding to the request for reading the message data is not equal to the sending message sequence number, or the read message When there is message data in the message queue corresponding to the request for data that has not been successfully read, the message data is read in the distributed Key-Va lue storage system. 8. The method of claim 7, wherein when the message queue is not read If the success message sequence number is not empty, there is message data in the message queue that has not been successfully read.  The method according to any one of claims 1 to 8, wherein if the message data is unsuccessfully read in the distributed Key-Va lue storage system, the message of the second distributed program is determined. Whether the delivery requires sequence guarantee, if sequence guarantee is required, continue to read the unread successful message data until the message data is successfully read; if sequence guarantee is not required, the message queue is not read The message serial number corresponding to the unread successful message data is recorded in the success message serial number, and the received message sequence number of the message queue is incremented, and the next message data is continuously read.  10. The method according to claim 9, wherein the second distributed is determined according to whether a value of the message queue is saved or a parameter in a request of the second distributed program to read message data Whether the program's messaging requires order guarantee.  The method according to claim 10, wherein the value of the message queue is guaranteed to be set by the first distributed program or the second distributed program by a message.  The method according to any one of claims 7-11, wherein, when the message queue corresponding to the request for reading the message data has message data that is not successfully read, the distributed The message data is read in the Key-Va 1 ue storage system, specifically:  Obtaining a message sequence number from the unread success message sequence number of the message queue corresponding to the request for reading the message data, and generating a key value Key including the message sequence number, according to the key value Key in the distribution The message data is read in the Key-Va lue storage system, and if the reading is successful, the message sequence number is deleted from the unread successful message sequence number of the message queue.  13. A cloud message service device, comprising:  An interface unit, configured to receive a message sent by the first distributed program, receive a request for reading the message data by the second distributed program, and send the message data read by the storage unit to the second distributed program;  a message queue management unit, configured to notify the storage unit to store the message data carried by the message received by the interface unit, and increment the sending message sequence number of the message queue corresponding to the message; and according to the read received by the interface unit Receiving a request for the message data, notifying the storage unit to read the message data, and incrementing the received message sequence number of the message queue when the message data corresponding to the sequence number of the received message of the message queue is successfully read; The storage unit includes a distributed Key-Va lue storage system for performing storage or reading of the message data. The cloud message service device according to claim 13, wherein the notification storage unit stores the message data carried by the message received by the interface unit, including:  Generating a key value Key of the sending message sequence number of the message queue corresponding to the message, and informing the storage unit to store, in the distributed Key-Va lue storage system, the interface received by the interface unit according to the key value Key Message data carried by the message; or  Notifying the storage unit to generate a key value Key including a sequence number of the sending message of the message queue corresponding to the message, and storing, in the distributed Key-Va lue storage system, the interface received by the interface unit according to the key value Key The message data carried by the message.  The cloud message service device according to any one of claims 13-14, wherein the notifying the storage unit to read the message data comprises:  Generating a key value Key of the received message sequence number of the message queue corresponding to the request for reading the message data, informing the storage unit to read the message in the distributed Key-Va lue storage system according to the key value Key Data; or,  Notifying the storage unit to generate a key value Key of the received message sequence number of the message queue corresponding to the request for reading the message data, and reading the key in the distributed Key-Va lue storage system according to the key value Key Message data.  The cloud message service device according to any one of claims 13-15, wherein the storage unit stores the transmission message sequence number and the received message sequence number of the message queue in a relational database.  The cloud message service device according to any one of claims 13-16, wherein the message sequence number of the message queue and the initial value of the received message sequence number are the same.  The cloud message service device according to any one of claims 13-17, wherein the sequence number of the message sent by the increment message queue, when the sequence number of the message sent exceeds the maximum value of the message sequence number, The sending message sequence number is reset to an initial value; or the incrementing the received message sequence number of the message queue, when the received message sequence number exceeds a maximum value of the message sequence number, the received message sequence number is reset Is the initial value.  The cloud message service device according to any one of claims 13 to 18, wherein if the received message sequence number of the message queue corresponding to the request for reading the message data is not equal to the message sequence number, or When there is message data in the message queue corresponding to the request for reading the message data that has not been successfully read, the message queue management unit notifies the storage unit to read the message data. 20. The cloud messaging service device of claim 19, wherein when the message If the unread success message sequence number of the queue is not empty, there is message data in the message queue that has not been successfully read.  The cloud message service device according to any one of claims 1 to 3, wherein if the storage unit reads the message data in the distributed Key-Va lue storage system is unsuccessful, the The message queue management unit determines whether the message delivery of the second distributed program requires order guarantee, and if the sequence guarantee is required, notifying the storage unit to continue reading the unread successfully message data until the read is successfully performed. Message data; if the sequence guarantee is not required, the message queue management unit records the message sequence number corresponding to the unread successful message data in the unread success message sequence number of the message queue, and increments the message sequence number The received message sequence number of the message queue notifies the storage unit to continue reading the next message data.  The cloud message service device according to claim 21, wherein the message queue management unit is configured to read a message data according to a value of the message queue or a second distributed program. The included parameters determine whether message delivery by the second distributed program requires order guarantee.  The cloud message service device according to any one of claims 11 to 9, wherein the value of the message queue is guaranteed by the message queue management unit according to the first distributed program or the second The messages of the distributed program are set.  The cloud message service device according to any one of claims 19 to 23, wherein, when there is unread message data in the message queue, the storage unit is notified to read the message data, specifically For:  The message queue management unit acquires a message sequence number from the unread success message sequence number of the message queue, generates a key value Key including the message sequence number, and notifies the storage unit according to the key value Key. Reading the message data in the distributed Key-Va lue storage system, if the reading is successful, the message queue management deletes the message serial number from the unread success message sequence number of the message queue .