CN111049729A - Persistent message transmission method and device - Google Patents

Persistent message transmission method and device Download PDF

Info

Publication number
CN111049729A
CN111049729A CN201911200387.4A CN201911200387A CN111049729A CN 111049729 A CN111049729 A CN 111049729A CN 201911200387 A CN201911200387 A CN 201911200387A CN 111049729 A CN111049729 A CN 111049729A
Authority
CN
China
Prior art keywords
message
memory
byte data
data stream
volatile memory
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN201911200387.4A
Other languages
Chinese (zh)
Inventor
陈仁革
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Suzhou Inspur Intelligent Technology Co Ltd
Original Assignee
Suzhou Inspur Intelligent Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Suzhou Inspur Intelligent Technology Co Ltd filed Critical Suzhou Inspur Intelligent Technology Co Ltd
Priority to CN201911200387.4A priority Critical patent/CN111049729A/en
Publication of CN111049729A publication Critical patent/CN111049729A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/07User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
    • H04L51/18Commands or executable codes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/568Storing data temporarily at an intermediate stage, e.g. caching
    • H04L67/5682Policies or rules for updating, deleting or replacing the stored data

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The invention discloses a persistent message transmission method and a device, comprising the following steps: receiving a persistent message from a producer to create a message storage object having message content and a message identifier; serializing the message storage object into a byte data stream by using an encapsulated writing method and storing the byte data stream into a nonvolatile memory; updating the message identifier and a physical pointer representing the logical location of the byte data stream in the non-volatile memory into an index page of the memory; receiving a message identifier to be searched from a consumer to determine a corresponding physical pointer in an index page of a memory; reading byte data streams in a nonvolatile memory based on a physical pointer and deserializing into message memory objects using an encapsulated read method; message content is extracted from the message storage object and fed back to the consumer for reading. The invention can improve the message transmission performance of the message middleware and meet the requirements of high reliability and high availability of the message middleware.

Description

Persistent message transmission method and device
Technical Field
The present invention relates to the field of switches, and in particular, to a persistent message transmission method and apparatus.
Background
The middleware is a kind of software between the application system and the system software, and it uses the basic service provided by the system software to connect each part of the application system or different applications on the network, so as to achieve the purpose of resource sharing. The message middleware is a middleware technology consisting of a message transmission mechanism or a message queue mode, performs platform-independent data communication by using an efficient and reliable message transmission mechanism, and performs integration of a distributed system based on data communication. With the increasingly deep information construction in China, more and more enterprises begin to enter the deep application stage, and middleware also caters to the prosperous and developing stage, and message middleware plays a vital role in the key application of many industries in China.
The message middleware should provide a level of reliability of selectable messages on the server side, i.e., persistent messages and non-persistent messages, which differ primarily in whether the message queue is stored on persistent storage. The persistent message refers to a message which is stored and then forwarded at the server side, and when the server fails or the service is abnormally quitted normally, the persistent message can be recovered after the service is started. In addition, in an application scenario where a user has a persistent subscription to a topic, if persistent storage of messages is not supported, the subscriber cannot receive messages that it publishes to the topic in an inactive state. The main purpose of persistent messages is to satisfy the high reliability and availability of message middleware. The persistence of current messages is primarily to store the messages in a local file, database, or distributed file system, as the interaction of message persistence with the file system affects the performance of the message middleware server.
The message middleware has high throughput performance by storing the messages sent by all the clients to the server in the memory, but when the server is down or the service is restarted, all the messages stored in the memory are lost, so that the high reliability and high availability of the messages cannot be ensured;
in a mode of storing all messages sent by the client to the server in the database, even if the server is down or the service is restarted, the message middleware can recover all messages which are not accepted by the client from the database, but the message throughput performance of the whole message middleware is seriously reduced due to database operation of frequently inserting and deleting message records into the database under the condition of high load; the additional database system reduces the processing power of the server and increases the cost to the user.
In a mode of storing all messages sent by the client to the server in a disk file system, when the server is down or the service is restarted, the message middleware can recover all messages which are not received by the client from the file system, but after the files are continuously read and written, file fragments can be caused, and the files can not be continuously used; meanwhile, files are directly operated, if file lock protection is not designed, once power failure and other accidents happen when the files are read and written, data abnormity and data inconsistency of the message files can be caused, the message files can not be used at the moment, and the purpose of message persistence is not achieved; in addition, the message throughput performance of the message middleware is greatly reduced due to the limitation of the performance of the file system.
Aiming at the problems of poor message transmission performance and low reliability and availability of message middleware in the prior art, no effective solution is available at present.
Disclosure of Invention
In view of this, an object of the embodiments of the present invention is to provide a persistent message transmission method and apparatus, which can improve the message transmission performance of a message middleware and meet the requirements of the message middleware on high reliability and high availability.
In view of the above object, a first aspect of the embodiments of the present invention provides a persistent message transmission method, including the following steps:
receiving a persistent message from a producer to create a message storage object having message content and a message identifier;
serializing the message storage object into a byte data stream by using an encapsulated writing method and storing the byte data stream into a nonvolatile memory;
updating the message identifier and a physical pointer representing the logical location of the byte data stream in the non-volatile memory into an index page of the memory;
receiving a message identifier to be searched from a consumer to determine a corresponding physical pointer in an index page of a memory;
reading byte data streams in a nonvolatile memory based on a physical pointer and deserializing into message memory objects using an encapsulated read method;
message content is extracted from the message storage object and fed back to the consumer for reading.
In some implementations, the index page includes an index tree having a plurality of leaf nodes, where each leaf node includes a message identifier for one byte data stream, a logical location of the byte data stream in non-volatile memory, and a physical pointer.
In some embodiments, the memory is located on a server that provides messaging middleware services for producers and consumers; the non-volatile memory is physically provided with one or more separate physical entities, which are all located on the server, or distributed across the server, one or more producer devices, and one or more consumer devices.
In some embodiments, index pages are reconstructed in memory based on non-volatile storage at reboot in response to a server going down or out of service.
In some embodiments, the non-volatile memory has an application program interface; storing the byte data stream into the non-volatile memory and reading the byte data stream in the non-volatile memory are both performed through an application program interface.
A second aspect of an embodiment of the present invention provides a persistent message transmission apparatus, including:
a processor; and
a memory storing program code executable by the processor, the program code when executed performing the steps of:
receiving a persistent message from a producer to create a message storage object having message content and a message identifier;
serializing the message storage object into a byte data stream by using an encapsulated writing method and storing the byte data stream into a nonvolatile memory;
updating the message identifier and a physical pointer representing the logical location of the byte data stream in the non-volatile memory into an index page of the memory;
receiving a message identifier to be searched from a consumer to determine a corresponding physical pointer in an index page of a memory;
reading byte data streams in a nonvolatile memory based on a physical pointer and deserializing into message memory objects using an encapsulated read method;
message content is extracted from the message storage object and fed back to the consumer for reading.
In some implementations, the index page includes an index tree having a plurality of leaf nodes, where each leaf node includes a message identifier for one byte data stream, a logical location of the byte data stream in non-volatile memory, and a physical pointer.
In some embodiments, the memory is located on a server that provides messaging middleware services for producers and consumers; the non-volatile memory is physically provided with one or more separate physical entities, which are all located on the server, or distributed across the server, one or more producer devices, and one or more consumer devices.
In some embodiments, index pages are reconstructed in memory based on non-volatile storage at reboot in response to a server going down or out of service.
In some embodiments, the non-volatile memory has an application program interface; storing the byte data stream into the non-volatile memory and reading the byte data stream in the non-volatile memory are both performed through an application program interface.
The invention has the following beneficial technical effects: the persistent message transmission method and device provided by the embodiment of the invention receive the persistent message from a producer to create a message storage object with message content and a message identifier; serializing the message storage object into a byte data stream by using an encapsulated writing method and storing the byte data stream into a nonvolatile memory; updating the message identifier and a physical pointer representing the logical location of the byte data stream in the non-volatile memory into an index page of the memory; receiving a message identifier to be searched from a consumer to determine a corresponding physical pointer in an index page of a memory; reading byte data streams in a nonvolatile memory based on a physical pointer and deserializing into message memory objects using an encapsulated read method; the technical scheme of extracting the message content from the message storage object and feeding the message content back to the consumer for reading can improve the message transmission performance of the message middleware and meet the requirements of high reliability and high availability of the message middleware.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a flow chart illustrating a persistent message transmission method according to the present invention;
fig. 2 is an index tree node diagram of the persistent message transmission method provided in the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the following embodiments of the present invention are described in further detail with reference to the accompanying drawings.
It should be noted that all expressions using "first" and "second" in the embodiments of the present invention are used for distinguishing two entities with the same name but different names or different parameters, and it should be noted that "first" and "second" are merely for convenience of description and should not be construed as limitations of the embodiments of the present invention, and they are not described in any more detail in the following embodiments.
In view of the foregoing, a first aspect of the embodiments of the present invention provides an embodiment of a persistent message transmission method capable of improving performance of message transmission of message middleware. Fig. 1 is a flow chart illustrating a persistent message transmission method provided by the present invention.
The persistent message transmission method, as shown in fig. 1, includes the following steps:
step S101: receiving a persistent message from a producer to create a message storage object having message content and a message identifier;
step S103: serializing the message storage object into a byte data stream by using an encapsulated writing method and storing the byte data stream into a nonvolatile memory;
step S105: updating the message identifier and a physical pointer representing the logical location of the byte data stream in the non-volatile memory into an index page of the memory;
step S107: receiving a message identifier to be searched from a consumer to determine a corresponding physical pointer in an index page of a memory;
step S109: reading byte data streams in a nonvolatile memory based on a physical pointer and deserializing into message memory objects using an encapsulated read method;
step S111: message content is extracted from the message storage object and fed back to the consumer for reading.
The message middleware message is stored in the nonvolatile memory in a persistent mode, so that the problem that memory data cannot be persisted is solved, the message middleware message is stored in the nonvolatile memory, and the problem that the message data are lost due to the fact that a server is down or the server is restarted in the traditional memory data storage is solved; secondly, the problem that the memory capacity is limited and a large amount of message data cannot be stored is solved, the single capacity of a nonvolatile memory (NVM) can be expanded by 3T, which is dozens of times of the capacity of the traditional NVM, and more message data can be stored; and thirdly, the problem of performance reduction of the message middleware in modes of file system persistent messages and the like is solved, the file system stores messages, data is exchanged between a high-speed memory and a low-bandwidth I/0 (input/output) device of the file system, the performance of the message middleware is seriously influenced, and the non-volatile memory NVM has performance close to that of a DRAM (traditional volatile memory).
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), a Random Access Memory (RAM), or the like. Embodiments of the computer program may achieve the same or similar effects as any of the preceding method embodiments to which it corresponds.
In some implementations, the index page includes an index tree having a plurality of leaf nodes, where each leaf node includes a message identifier for one byte data stream, a logical location of the byte data stream in non-volatile memory, and a physical pointer.
In some embodiments, the memory is located on a server that provides messaging middleware services for producers and consumers; the non-volatile memory is physically provided with one or more separate physical entities, which are all located on the server, or distributed across the server, one or more producer devices, and one or more consumer devices.
In some embodiments, index pages are reconstructed in memory based on non-volatile storage at reboot in response to a server going down or out of service.
In some embodiments, the non-volatile memory has an application program interface; storing the byte data stream into the non-volatile memory and reading the byte data stream in the non-volatile memory are both performed through an application program interface.
The method disclosed according to an embodiment of the present invention may also be implemented as a computer program executed by a CPU (central processing unit), and the computer program may be stored in a computer-readable storage medium. The computer program, when executed by the CPU, performs the above-described functions defined in the method disclosed in the embodiments of the present invention. The above-described method steps and system elements may also be implemented using a controller and a computer-readable storage medium for storing a computer program for causing the controller to implement the functions of the above-described steps or elements.
The following further illustrates embodiments of the invention in terms of specific examples as shown in fig. 2.
As shown in fig. 2, in the embodiment of the present invention, a message is received from a producer, a message storage object AddMessage is created by using the message as a parameter, a message field is used as a message to be stored, a message id is used as a message identifier, and the message id is a unique identifier of a message for storing, searching, and deleting the message. And then serializing the created Message object AddMessage into a byte data stream, wherein the AddMessage encapsulates a method for serializing and deserializing Message _ write and Message _ read, the Message _ write method serializes the Message object into a byte stream, and the Message _ read deserializes the byte stream into the AddMessage object, so that the storage and reading of the AddMessage object are realized. Writing the byte stream into the NVM, updating the index page in the memory, inserting the message identifier and pointer (corresponding to the message data position) into the node in the index tree, storing the index information in the leaf node of the index tree, where key (String in FIG. 2) corresponds to the message identifier, value (RAW in FIG. 2) corresponds to the position of the message in the NVM, and the pointer records the address of the value. Every time the message is written, the index information in the index tree is updated.
When a consumer tries to acquire information, the position of a message data storage address space is searched through a message identifier and a pointer, message data are read, a read byte stream is deserialized into a message object AddMessage, and the message is further taken out of the message object AddMessage.
As can be seen from the foregoing embodiments, the persistent message transmission method provided by the embodiments of the present invention creates a message storage object having message content and a message identifier by receiving a persistent message from a producer; serializing the message storage object into a byte data stream by using an encapsulated writing method and storing the byte data stream into a nonvolatile memory; updating the message identifier and a physical pointer representing the logical location of the byte data stream in the non-volatile memory into an index page of the memory; receiving a message identifier to be searched from a consumer to determine a corresponding physical pointer in an index page of a memory; reading byte data streams in a nonvolatile memory based on a physical pointer and deserializing into message memory objects using an encapsulated read method; the technical scheme of extracting the message content from the message storage object and feeding the message content back to the consumer for reading can improve the message transmission performance of the message middleware and meet the requirements of high reliability and high availability of the message middleware.
It should be particularly noted that, the steps in the embodiments of the persistent message transmission method described above can be mutually intersected, replaced, added, or deleted, and therefore, these reasonable permutation and combination transformations for the persistent message transmission method should also belong to the scope of the present invention, and should not limit the scope of the present invention to the described embodiments.
In view of the above object, according to a second aspect of the embodiments of the present invention, an embodiment of a persistent message transmission apparatus capable of improving performance of message transmission of message middleware is provided. The persistent message transmission apparatus includes:
a processor; and
a memory storing program code executable by the processor, the program code when executed performing the steps of:
receiving a persistent message from a producer to create a message storage object having message content and a message identifier;
serializing the message storage object into a byte data stream by using an encapsulated writing method and storing the byte data stream into a nonvolatile memory;
updating the message identifier and a physical pointer representing the logical location of the byte data stream in the non-volatile memory into an index page of the memory;
receiving a message identifier to be searched from a consumer to determine a corresponding physical pointer in an index page of a memory;
reading byte data streams in a nonvolatile memory based on a physical pointer and deserializing into message memory objects using an encapsulated read method;
message content is extracted from the message storage object and fed back to the consumer for reading.
In some implementations, the index page includes an index tree having a plurality of leaf nodes, where each leaf node includes a message identifier for one byte data stream, a logical location of the byte data stream in non-volatile memory, and a physical pointer.
In some embodiments, the memory is located on a server that provides messaging middleware services for producers and consumers; the non-volatile memory is physically provided with one or more separate physical entities, which are all located on the server, or distributed across the server, one or more producer devices, and one or more consumer devices.
In some embodiments, index pages are reconstructed in memory based on non-volatile storage at reboot in response to a server going down or out of service.
In some embodiments, the non-volatile memory has an application program interface; storing the byte data stream into the non-volatile memory and reading the byte data stream in the non-volatile memory are both performed through an application program interface.
As can be seen from the above embodiments, the persistent message transmission apparatus provided by the embodiments of the present invention creates a message storage object having message content and a message identifier by receiving a persistent message from a producer; serializing the message storage object into a byte data stream by using an encapsulated writing method and storing the byte data stream into a nonvolatile memory; updating the message identifier and a physical pointer representing the logical location of the byte data stream in the non-volatile memory into an index page of the memory; receiving a message identifier to be searched from a consumer to determine a corresponding physical pointer in an index page of a memory; reading byte data streams in a nonvolatile memory based on a physical pointer and deserializing into message memory objects using an encapsulated read method; the technical scheme of extracting the message content from the message storage object and feeding the message content back to the consumer for reading can improve the message transmission performance of the message middleware and meet the requirements of high reliability and high availability of the message middleware.
It should be particularly noted that the above-mentioned embodiment of the persistent message transmission apparatus employs the embodiment of the persistent message transmission method to specifically describe the working process of each module, and those skilled in the art can easily think that these modules are applied to other embodiments of the persistent message transmission method. Of course, since the steps in the embodiment of the persistent message transmission method may be mutually intersected, replaced, added, or deleted, these reasonable permutation and combination transformations should also belong to the scope of the present invention for the persistent message transmission apparatus, and should not limit the scope of the present invention to the embodiment.
The foregoing is an exemplary embodiment of the present disclosure, but it should be noted that various changes and modifications could be made herein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps and/or actions of the method claims in accordance with the disclosed embodiments described herein need not be performed in any particular order. Furthermore, although elements of the disclosed embodiments of the invention may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.
It should be understood that, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly supports the exception. It should also be understood that "and/or" as used herein is meant to include any and all possible combinations of one or more of the associated listed items. The numbers of the embodiments disclosed in the embodiments of the present invention are merely for description, and do not represent the merits of the embodiments.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
Those of ordinary skill in the art will understand that: the discussion of any embodiment above is meant to be exemplary only, and is not intended to intimate that the scope of the disclosure, including the claims, of embodiments of the invention is limited to these examples; within the idea of an embodiment of the invention, also technical features in the above embodiment or in different embodiments may be combined and there are many other variations of the different aspects of an embodiment of the invention as described above, which are not provided in detail for the sake of brevity. Therefore, any omissions, modifications, substitutions, improvements, and the like that may be made without departing from the spirit and principles of the embodiments of the present invention are intended to be included within the scope of the embodiments of the present invention.

Claims (10)

1. A method for persistent message transmission, comprising the steps of:
receiving a persistent message from a producer to create a message storage object having message content and a message identifier;
serializing the message memory object into a byte data stream using an encapsulated write method and storing the byte data stream into a non-volatile memory;
updating the message identifier and a physical pointer representing the logical location of the byte data stream in the non-volatile memory into an index page of memory;
receiving a message identifier to be looked up from a consumer to determine a corresponding physical pointer in the index page of the memory;
reading the byte data stream in the non-volatile memory based on the physical pointer and deserializing into the message memory object using an encapsulated read method;
and extracting the message content from the message storage object and feeding back the message content to a consumer for reading.
2. The method of claim 1, wherein the index page comprises an index tree having a plurality of leaf nodes, wherein each leaf node comprises the message identifier of one of the byte data streams, a logical location of the byte data stream in the non-volatile memory, and the physical pointer.
3. The method of claim 1, wherein the memory is located on a server that provides messaging middleware services for producers and consumers; the non-volatile memory is physically provided with one or more separate physical entities, which are all disposed on the server or distributed on the server, one or more producer devices, and one or more consumer devices.
4. The method of claim 3, wherein the index pages are reconstructed in the memory based on the non-volatile storage at reboot in response to the server going down or out of service.
5. The method of claim 3, wherein the non-volatile memory has an application program interface; storing the byte data stream into a non-volatile memory and reading the byte data stream in the non-volatile memory are both performed through the application program interface.
6. A persistent message transmission apparatus, comprising:
a processor; and
a memory storing program code executable by the processor, the program code when executed performing the steps of:
receiving a persistent message from a producer to create a message storage object having message content and a message identifier;
serializing the message memory object into a byte data stream using an encapsulated write method and storing the byte data stream into a non-volatile memory;
updating the message identifier and a physical pointer representing the logical location of the byte data stream in the non-volatile memory into an index page of memory;
receiving a message identifier to be looked up from a consumer to determine a corresponding physical pointer in the index page of the memory;
reading the byte data stream in the non-volatile memory based on the physical pointer and deserializing into the message memory object using an encapsulated read method;
and extracting the message content from the message storage object and feeding back the message content to a consumer for reading.
7. The apparatus of claim 6, wherein the index page comprises an index tree having a plurality of leaf nodes, wherein each leaf node comprises the message identifier of one of the byte data streams, a logical location of the byte data stream in the non-volatile memory, and the physical pointer.
8. The apparatus of claim 6, wherein the memory is located on a server that provides messaging middleware services for producers and consumers; the non-volatile memory is physically provided with one or more separate physical entities, which are all disposed on the server or distributed on the server, one or more producer devices, and one or more consumer devices.
9. The apparatus of claim 8, wherein the index pages are reconstructed in the memory based on the non-volatile storage at reboot in response to the server going down or out of service.
10. The apparatus of claim 8, wherein the non-volatile memory has an application program interface; storing the byte data stream into a non-volatile memory and reading the byte data stream in the non-volatile memory are both performed through the application program interface.
CN201911200387.4A 2019-11-29 2019-11-29 Persistent message transmission method and device Pending CN111049729A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911200387.4A CN111049729A (en) 2019-11-29 2019-11-29 Persistent message transmission method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911200387.4A CN111049729A (en) 2019-11-29 2019-11-29 Persistent message transmission method and device

Publications (1)

Publication Number Publication Date
CN111049729A true CN111049729A (en) 2020-04-21

Family

ID=70234178

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911200387.4A Pending CN111049729A (en) 2019-11-29 2019-11-29 Persistent message transmission method and device

Country Status (1)

Country Link
CN (1) CN111049729A (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111784329A (en) * 2020-06-30 2020-10-16 京东数字科技控股有限公司 Service data processing method and device, storage medium and electronic device
CN113176896A (en) * 2021-03-19 2021-07-27 中盈优创资讯科技有限公司 Method for randomly taking out object based on single-in single-out lock-free queue
CN114244899A (en) * 2021-12-02 2022-03-25 上海微盟企业发展有限公司 Message transmission method and device and readable storage medium
CN114895987A (en) * 2022-07-08 2022-08-12 英诺达(成都)电子科技有限公司 Message processing method, device, equipment and computer storage medium
CN114979249A (en) * 2022-03-30 2022-08-30 阿里巴巴(中国)有限公司 Message handle creating method, message pushing method, related device and system

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101233480A (en) * 2005-08-03 2008-07-30 桑迪士克股份有限公司 Reprogrammable non-volatile memory systems with indexing of directly stored data files
EP2039129A1 (en) * 2006-06-27 2009-03-25 International Business Machines Corporation Reliable messaging using redundant message streams in a high speed, low latency data communications environment
US7716525B1 (en) * 2006-07-24 2010-05-11 Solace Systems, Inc. Low latency, high throughput data storage system
CN101707633A (en) * 2009-11-27 2010-05-12 山东中创软件商用中间件股份有限公司 Message-oriented middleware persistent message storing method based on file system
CN103098034A (en) * 2010-07-28 2013-05-08 Fusion-Io股份有限公司 Apparatus, system, and method for conditional and atomic storage operations
CN105446899A (en) * 2015-11-09 2016-03-30 上海交通大学 Memory data quick persistence method based on storage-class memory
CN109614372A (en) * 2018-10-26 2019-04-12 阿里巴巴集团控股有限公司 A kind of object storage, read method, device and service server
CN110413724A (en) * 2019-06-18 2019-11-05 苏州浪潮智能科技有限公司 A kind of data retrieval method and device

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101233480A (en) * 2005-08-03 2008-07-30 桑迪士克股份有限公司 Reprogrammable non-volatile memory systems with indexing of directly stored data files
EP2039129A1 (en) * 2006-06-27 2009-03-25 International Business Machines Corporation Reliable messaging using redundant message streams in a high speed, low latency data communications environment
US7716525B1 (en) * 2006-07-24 2010-05-11 Solace Systems, Inc. Low latency, high throughput data storage system
CN101707633A (en) * 2009-11-27 2010-05-12 山东中创软件商用中间件股份有限公司 Message-oriented middleware persistent message storing method based on file system
CN103098034A (en) * 2010-07-28 2013-05-08 Fusion-Io股份有限公司 Apparatus, system, and method for conditional and atomic storage operations
CN105446899A (en) * 2015-11-09 2016-03-30 上海交通大学 Memory data quick persistence method based on storage-class memory
CN109614372A (en) * 2018-10-26 2019-04-12 阿里巴巴集团控股有限公司 A kind of object storage, read method, device and service server
CN110413724A (en) * 2019-06-18 2019-11-05 苏州浪潮智能科技有限公司 A kind of data retrieval method and device

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111784329A (en) * 2020-06-30 2020-10-16 京东数字科技控股有限公司 Service data processing method and device, storage medium and electronic device
CN111784329B (en) * 2020-06-30 2024-04-05 京东科技控股股份有限公司 Service data processing method and device, storage medium and electronic device
CN113176896A (en) * 2021-03-19 2021-07-27 中盈优创资讯科技有限公司 Method for randomly taking out object based on single-in single-out lock-free queue
CN114244899A (en) * 2021-12-02 2022-03-25 上海微盟企业发展有限公司 Message transmission method and device and readable storage medium
CN114244899B (en) * 2021-12-02 2024-05-17 上海微盟企业发展有限公司 Message transmission method, device and readable storage medium
CN114979249A (en) * 2022-03-30 2022-08-30 阿里巴巴(中国)有限公司 Message handle creating method, message pushing method, related device and system
CN114895987A (en) * 2022-07-08 2022-08-12 英诺达(成都)电子科技有限公司 Message processing method, device, equipment and computer storage medium
CN114895987B (en) * 2022-07-08 2022-09-30 英诺达(成都)电子科技有限公司 Message processing method, device, equipment and computer storage medium

Similar Documents

Publication Publication Date Title
CN111049729A (en) Persistent message transmission method and device
RU2471227C2 (en) Peer-to-peer synchronisation assisted with service unit
US10554604B1 (en) Low-load message queue scaling using ephemeral logical message topics
CN111580884B (en) Configuration updating method, device, server and electronic equipment
US20120254118A1 (en) Recovery of tenant data across tenant moves
CN102349062A (en) Programming model for synchronizing browser caches across devices and web services
CN111736775A (en) Multi-source storage method, device, computer system and storage medium
US20080281920A1 (en) Adaptive parsing and compression of soap messages
CN115129736A (en) Rule engine-based rule event dynamic loading and updating method and related equipment
CN111064626B (en) Configuration updating method, device, server and readable storage medium
CN108255994A (en) A kind of database version management method based on database snapshot
US10298656B2 (en) Extending representational state transfer application program interface (REST API) functionality
US11178197B2 (en) Idempotent processing of data streams
CN113434506B (en) Data management and retrieval method, device, computer equipment and readable storage medium
US11755555B2 (en) Storing an ordered associative array of pairs using an append-only storage medium
CN111666045A (en) Data processing method, system, equipment and storage medium based on Git system
CN111625617A (en) Data indexing method and device and computer readable storage medium
CN116760661A (en) Data storage method, apparatus, computer device, storage medium, and program product
US7363322B2 (en) Methods and systems for performing reliable asynchronous notification of high-level document operations
CN113448757B (en) Message processing method, device, equipment, storage medium and system
CN113051244B (en) Data access method and device, and data acquisition method and device
US11656972B1 (en) Paginating results obtained from separate programmatic interfaces
CN112131201B (en) Method, system, equipment and medium for high availability of network additional storage
CN114218013A (en) Searching method, searching device and electronic equipment storage medium
US11017032B1 (en) Document recovery utilizing serialized data

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication

Application publication date: 20200421

RJ01 Rejection of invention patent application after publication