CN109067844A - A kind of message communication system - Google Patents
A kind of message communication system Download PDFInfo
- Publication number
- CN109067844A CN109067844A CN201810745624.4A CN201810745624A CN109067844A CN 109067844 A CN109067844 A CN 109067844A CN 201810745624 A CN201810745624 A CN 201810745624A CN 109067844 A CN109067844 A CN 109067844A
- Authority
- CN
- China
- Prior art keywords
- message
- server
- unit
- client
- queue
- 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
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
- H04L67/5681—Pre-fetching or pre-delivering data based on network characteristics
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1073—Registration or de-registration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
- H04L67/5682—Policies or rules for updating, deleting or replacing the stored data
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Multimedia (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a kind of message communication systems, including client and server-side, the client is remotely connect with the server-side, the client includes several producer's clients and several consumer clients, the server-side includes a registration center and several message servers, the registration center is separately connected each message server, and controls each server；The message data being stored in the message server belongs to multiple and different message subjects, and each message subject is respectively associated in multiple parallel message queues.The beneficial effect of above-mentioned technical proposal is: increasing message capacity by increasing the message queue of identical message theme newly, multiple message queues work at the same time to reduce the time-consuming of Message Processing, to save the time, accelerate Message Processing speed and increase the stability of system.
Description
Technical field
The present invention relates to message call technical field more particularly to a kind of message communication systems.
Background technique
Traditional message communication system is mainly to maintain long connection, message server active push message to consumer client
Hold end.Main function is, in order to guarantee that message is only primary by consumption, to record the state that message has been consumed during push.
However existing message communication system is greater than the consumption of consumer client in the message that producer's client generates
When ability, the memory that message communication middleware can be made to occupy constantly increases, and keeps message communication middleware unstable, similar disappear occurs
Breath loses or the failure of message queue blocking, it is therefore desirable to which a kind of storage capacity problem that can solve message communication system disappears
Cease communication system.
Summary of the invention
For the above-mentioned problems in the prior art, a kind of technical solution of message communication system is now provided, it is intended to logical
The message queue of newly-increased identical message theme is crossed to increase message capacity, multiple message queues work at the same time to reduce Message Processing
Time-consuming accelerate Message Processing speed and increase the stability of system to save the time.
Specific technical solution is as follows:
A kind of message communication system, including client and server-side, the client are remotely connect with the server-side,
In, the client includes several producer's clients and several consumer clients, and producer's client is used for institute
Server-side write-in message data is stated, the consumer client is for transferring message data from told server-side；
The server-side includes a registration center and several message servers, and the registration center is separately connected each described
Message server, and each server is controlled；
The registration center is for registering online producer's client, consumer client and message server
For online equipment；
The message data being stored in the message server belongs to multiple and different message subjects, each described
Message subject is respectively associated in multiple parallel message queues；
Producer's client is by way of being written the message data to message queue described at least one to institute
The message data is written in the message server stated in server-side；
The consumer client is by from least one the described message queue for being assigned to the consumer client
The mode for reading the message data reads the message data from the message server in the server-side and disappears
Take.
Preferably, message communication system, wherein the message server includes a message sink interface, the message
Receiving interface receives message, and by the asynchronous persistent storage of the message received into a message logging；The message server
Including the information query interface for Consumer System recalls information.
Preferably, message communication system, wherein the registration center specifically includes:
Storage unit includes the registration column of online and successful registration the online equipment in the storage unit
Table；
Monitoring unit connects the storage unit, for monitoring the online equipment in real time by the way of heartbeat monitor,
And export real-time monitored results；
Updating unit is separately connected the storage unit and the monitoring unit, for being judged according to the monitored results
With the presence or absence of there is the online equipment to go offline, and the register list is updated according to judging result；
Notification unit is separately connected the updating unit and the storage unit, for the updating unit every time more
After the new register list, the updated register list is notified to each online equipment.
Preferably, message communication system, wherein the information query interface is by pulling mode to message server tune
Use message data.
Preferably, message communication system, wherein the registration center is synchronous with the message subject by corresponding message
Queue number is stored to message server.
Preferably, message communication system, wherein the producer is disappeared by the way of poll to described at least one
Breath queue is written the message server of the mode of the message data into the server-side and the message data is written.
Preferably, message communication system, wherein the registration center further include:
Acquiring unit is asked for obtaining the message read requests of the consumer client, and according to message reading
Processing is asked to obtain the quantity for being associated with the consumer client of each message subject；
Allocation unit, connects the acquiring unit, and the allocation unit is directed to each message subject, to needing to read
At least one not mutual duplicate described message queue of each of message subject consumer client's distribution.
Preferably, message communication system, wherein each message server respectively includes a memory space, described
Multiple storage files are preserved in memory space, the storage file and the message queue correspond, each storage
File is respectively used to save data file pointed by the message data in the corresponding message queue.
Preferably, message communication system, wherein be respectively set one for each message subject and retry queue；
The registration center further include:
Judging unit is read, for judging that the consumer client reads whether the message data succeeds, and is exported
Corresponding judging result；
Unit is retried, the reading judging unit is connected, for will read described in failure and disappear according to the judging result
Breath data retry in queue described in being put into corresponding to the message data, and it is described heavy to allow the consumer client to pass through
It tries queue and reads the message data.
Preferably, message communication system, wherein the registration center further include:
Counting unit, retries unit described in connection, and the counting unit is for recording the consumer client from described
Retry the number that the message data failure is read in queue；
When the number of counting unit record is more than a preset times, the unit that retries refuses the consumer visitor
Family end continues to read, and judges that this message data reads failure, and the message data is then put into a dead letter queue
In.
Above-mentioned technical proposal has the following advantages that or the utility model has the advantages that provides a kind of message communication system, can be by newly-increased
The message queue of identical message theme increases message capacity, and multiple message queues work at the same time to reduce the consumption of Message Processing
When, to save the time, accelerate Message Processing speed and increase the stability of system.
Detailed description of the invention
With reference to appended attached drawing, more fully to describe the embodiment of the present invention.However, appended attached drawing be merely to illustrate and
It illustrates, and is not meant to limit the scope of the invention.
Fig. 1 is a kind of structural representation Fig. 1 of message communication system embodiment of the present invention；
Fig. 2 is a kind of structural representation Fig. 2 of message communication system embodiment of the present invention；
Appended drawing reference: 1, client；2, server-side；3, producer's client；4, consumer client；5, registration center；
6, message server；7, message subject；8, message queue.
Specific embodiment
Following will be combined with the drawings in the embodiments of the present invention, and technical solution in the embodiment of the present invention carries out clear, complete
Site preparation description, it is clear that described embodiments are only a part of the embodiments of the present invention, instead of all the embodiments.It is based on
Embodiment in the present invention, those of ordinary skill in the art without creative labor it is obtained it is all its
His embodiment, shall fall within the protection scope of the present invention.
It should be noted that in the absence of conflict, the feature in embodiment and embodiment in the present invention can phase
Mutually combination.
The present invention will be further explained below with reference to the attached drawings and specific examples, but not as the limitation of the invention.
As shown in Figs. 1-2, a kind of message communication system, including client 1 and server-side 2, the client 1 and the clothes
Being engaged in, end 2 is long-range to be connected, and the client 1 includes several producer's clients 3 and several consumer clients 4, the producer
Client 3 is used to that message data to be written to the server-side 2, and the consumer client 4 from told server-side 2 for transferring
Message data；
The server-side 2 includes a registration center 5 and several message servers 6, and the registration center 5 is separately connected each
The message server 6, and each server is controlled；
The registration center 5 is used for 6 note of online producer's client 3, consumer client 4 and message server
Volume becomes online equipment；
The message data being stored in the message server 6 belongs to multiple and different message subjects 7, Mei Gesuo
Message subject 7 is stated to be respectively associated in multiple parallel message queues 8；
Producer's client 3 by way of the message data is written to message queue 8 described at least one to
The message data is written in the message server 6 in the server-side 2；
The consumer client 4 is by from least one the described message team for being assigned to the consumer client 4
The mode that column 8 read the message data reads the message data from the message server 6 in the server-side 2 and goes forward side by side
Row consumption.
The message server 6 includes a message sink interface, the message sink interface message, and will receive
The asynchronous persistent storage of message into a message logging；The message server 6 includes being used for Consumer System recalls information
Information query interface.
It should be noted that producer's client 3 and the identity of consumer client 4 be it is fixed, i.e., can between them
Mutually to convert, such as producer's client 3 can be converted into consumer client 4, and certain consumer client 4 can also turn
Turn to producer's client 3.
Several message servers 6 are distributed type assemblies in the present embodiment.
It should be noted that distributed type assemblies are to realize set expandability and highly reliable important technical.It is distributed
Group system includes multiple nodes (each message server 6 of the present embodiment middle finger), wherein any one or more nodes occur
When failure, entire cluster still be can work normally.It is more that so-called distribution refers to that the important control information of cluster is distributed across
On a node, to improve the whole reliability of cluster.
In the present embodiment, each message server 6 is reciprocity, and each message server 6, which can be provided externally, to be deposited
Take service.To which when the storage of some message server 6 is broken down, distributed type assemblies can also adapt to and just automatically
Often operating, while this variation be to the registration center 5 on upper layer it is transparent, registration center 5 still can be according to preset mode
Storage system is accessed, thus, the reliabilty and availability of whole system improves.
In the present embodiment, several message servers 6 are distributed type assemblies, even if at least one message server 6 is for some reason
Hinder and exit, can also rejoin, has ensured the stability of system.
The registration center 5 specifically includes:
Storage unit includes the registration column of online and successful registration the online equipment in the storage unit
Table；
Monitoring unit connects the storage unit, for monitoring the online equipment in real time by the way of heartbeat monitor,
And export real-time monitored results；
Updating unit is separately connected the storage unit and the monitoring unit, for being judged according to the monitored results
With the presence or absence of there is the online equipment to go offline, and the register list is updated according to judging result；
Notification unit is separately connected the updating unit and the storage unit, for the updating unit every time more
After the new register list, the updated register list is notified to each online equipment.
In a specific embodiment, consumer client 4 sends registration request to registration center 5 in its unlatching first
To be registered.Consumer client 4 obtains unique accession designation number after registration center 5 succeeds in registration, i.e. consumer visitor
Family end 4 is online to become online equipment, and just there are the corresponding letters of the consumer client 4 in the storage unit of registration center 5
It ceases and generates new register list, to carry out heartbeat monitor to the consumer client 4 in monitoring unit.
In the embodiment, the monitoring unit of registration center 5 monitors (such as the consumer of online equipment when generating service change
Client 4 stops service for some reason), registration center 5 obtains the information and is updated by notification unit to register list,
And online equipment is set to can refer to the different conditions variation of member to each online equipment dispatch order updated register list
Make dimension stability adjustment appropriate.
In the embodiment, gone offline when the monitoring unit of above-mentioned registration center 5 monitors online equipment (such as consumer visitor
Family end 4 stops service), the updating unit of registration center 5 updates register list according to the notice, such as online sets what is gone offline
Standby corresponding registration information (accession designation number of online equipment is referred specifically in the present embodiment) is deleted from register list.
In the embodiment, above-mentioned registration center 5 first according to different producer's clients 3 or consumer client 4 or
The registration information that message server 6 is sent registers it, and forms the register list including all online equipment.Change speech
It, consumer client 4 can be by browsing the register list come gathering information.
In the embodiment, when above-mentioned registration center 5 receives new registration information, register list is updated, with
Add new related registration information.
The information query interface calls message data to message server 6 by way of pulling.
The mode of pulling can pull message data to message server 6 when system available free resource, guarantee consumer visitor
The stability at family end 4.
The registration center 5 is synchronous with the message subject 7 to arrive message server for the number storage of corresponding message queue 8
6。
The side of the message data is written to message queue 8 described at least one by the way of poll by the producer
The message data is written in the message server 6 of the formula into the server-side 2.
In the present embodiment, the producer is sequentially inquired whether each message queue 8 needs to be written and is disappeared by the way of poll
Data are ceased, has to give and services, next message queue 8 is inquired again after service, then constantly in cycles.
The registration center 5 further include:
Acquiring unit is asked for obtaining the message read requests of the consumer client 4, and according to message reading
Processing is asked to obtain the quantity for being associated with the consumer client 4 of each message subject 7；
Allocation unit, connects the acquiring unit, and the allocation unit is directed to each message subject 7, to needing to read
Take at least one not mutual duplicate described message queue 8 of each of described message subject 7 distribution of consumer client 4.
Specifically, in preferred embodiment of the invention, when acquiring unit gets the consumption of each message subject 7
After the quantity of person's client 4, notice allocation unit is for each described at least one not mutual duplicate institute of the distribution of message subject 7
Message queue 8 is stated to each consumer client 4 under message subject 7, each consumer client 4, which can call, to be assigned to
Message queue 8 is to read corresponding message data.
Specifically, in preferred embodiment of the invention, consumer client 4 needs to read disappearing for a certain message subject 7
When ceasing queue 8, consumer client 4 sends message read requests to registration center 5, and acquiring unit obtains the reading of these message and asks
It asks, and is handled to obtain the quantity for the consumer client 4 for being associated with corresponding message subject 7 according to the message read requests
Afterwards, for each distribution of message subject 7, at least one duplicate described message queue 8 is not disappeared notice allocation unit mutually
Each consumer client 4 under theme 7 is ceased, prevents 2 consumer clients 4 from pulling the same queue, it is therefore an objective to prevent from disappearing
Double Spending is ceased, each consumer client 4 can call the message queue being assigned to 8 to read corresponding message count at this time
According to.
The size that consumer client 4 can configure according to system resource, active inquiry message, than if any a transaction class
The theme of type, message server 6 are which create 8 message queues 8, then consumer client 4 can obtain upon registration
The reversion of this 8 message queues 8 indicates that consumer client 4 can obtain message from this 8 message queues 8.
Each message server 6 respectively includes a memory space, and multiple storage texts are preserved in the memory space
Part, the storage file and the message queue 8 correspond, and each storage file is respectively used to save corresponding described
Data file pointed by the message data in message queue 8.
In the present embodiment, the logic query of message is equivalent to the catalogue of dictionary, is used to specify message in physical file
Position on MessageLog.
Each queue under each message subject 7 has a corresponding MessageQueue file, store path $
{ MessageHome }/msgstore/messagequeue/ $ { message subject 777 }/$ { queueId }/$ { filename }, message
The file organization of queue 8 is as follows,
-messageLog
|-00000002253645678215
|-00000002253645678216
|-00000002253645678217
-messagequeue
|-DLQConsumerGroupA
|-0
|-0000000000000053345534
|-RETRYConsumerGroupA
|-0
|-0000000000000053234125
|-RETRYConsumerGroupB
|-0
|-0000000000000054523152
|-mq_topic_dispatch
|-0
|-0000000545885225458662
|-1
|-0000000545885225458663
|-2
|-0000000545885225458664
|-mq_topic_resume
|-0
|-0000000545885225458665
|-1
|-0000000545885225458666
|-2
|-0000000545885225458667
Such as in the present embodiment, the message subject 77 of mq_topic_dispatch has 3 queues 0,1,2, then mq_
The composition of topic_disaptch and 0 one messagequeue, mq_topic_disaptch and 0 forms another
messagequeue。
It should be noted that storage unit is the binary system of a 12 byte fixed length in messagequeue in the present embodiment
Data, the storage unit in messagequeue includes Offset and Size, and the meaning that Offset is represented exists as this message
Real offset in MessageLog file, the length is 8 bytes；The meaning that Size is represented exists as this message
Message size in MessageLog file, the length is 4 bytes.
Message logging stores the physical file of message, the MessageLog file on each message server 6 is by the machine
All message queues 8 are shared.The storage catalogue of MessageLog file is $ { MessageHome }/msgstore/
The data length of messagelog/ { filename }, message storage are not fixed, and document order is write, message storage structure such as the following table 1
It is shown, it is successively stored according to number order and the corresponding content of number.
Table 1
One, which is respectively set, for each message subject 7 retries queue；
The registration center 5 further include:
Judging unit is read, for judging that the consumer client 4 reads whether the message data succeeds, and is exported
Corresponding judging result；
Unit is retried, the reading judging unit is connected, for will read described in failure and disappear according to the judging result
Breath data retry in queue described in being put into corresponding to the message data, and it is described to allow the consumer client 4 to pass through
It retries queue and reads the message data.
Abnormal message data is read for placing it should be noted that retrying queue.
If consumer client 4 prompts consumption failure in the present embodiment, message will be addressed to and retry in queue
RETRYConsumerGroupA。
The registration center 5 further include:
Counting unit, retries unit described in connection, and the counting unit is for recording the consumer client 4 from described
Retry the number that the message data failure is read in queue；
When the number of counting unit record is more than a preset times, the unit that retries refuses the consumer visitor
Family end 4 continues to read, and judges that this message data reads failure, and the message data is then put into a dead letter queue
In.
It should be noted that dead letter queue is for placing the message data that can not be transmitted for some reason.
In the present embodiment, if consumer client 4 reads demagnetization data failure, and after retrying predetermined number of times, such as
Preset times are 5 times, if consumer client 4 still fails after reading 5 times, are sent to dead letter DLQConsumerGroupA；
Such as preset times are 10 times, if consumer client 4 still fails after reading 10 times, are sent to the dead letter
DLQConsumerGroupA。
The storage for solving message communication system in this example by increasing the message queue 8 of identical message subject 7 newly is held
Amount problem.For example the received message of queue A is the theme of transaction class, message queue 8Aa setting maximum storage, which can consume message, is
100mb, because message carrier is likely to be breached 1mb, and consumption terminal receives Message Processing and takes a long time, and message queue 8A is caused to occupy
Memory reaches 100mb, in order to guarantee that system is stablized, therefore to increase theme of the queue Ab as message queue 88Aa newly,
To make message capacity be promoted to 200mb.
In this example, a kind of data flow of message communication system is shown in steps are as follows:
1. message data is written toward message server 6 in producer's client 3；
2. message server 6 receives message data, asynchronous write to local disk persistence；
3. consumer client 4 reads message data；
4. message server 6 records consumer client 4 and has read message offset position.
The foregoing is merely preferred embodiments of the present invention, are not intended to limit embodiments of the present invention and protection model
It encloses, to those skilled in the art, should can appreciate that all with made by description of the invention and diagramatic content
Equivalent replacement and obviously change obtained scheme, should all be included within the scope of the present invention.
Claims (10)
1. a kind of message communication system, including client and server-side, the client are remotely connect with the server-side, special
Sign is,
The client includes several producer's clients and several consumer clients, and producer's client is used for institute
Server-side write-in message data is stated, the consumer client is for transferring message data from told server-side；
The server-side includes a registration center and several message servers, and the registration center is separately connected each message
Server, and each server is controlled；
The registration center is for online producer's client, consumer client and message server to be registered as
Line equipment；
The message data being stored in the message server belongs to multiple and different message subjects, each message
Theme is respectively associated in multiple parallel message queues；
Producer's client is by way of being written the message data to message queue described at least one to the clothes
The message data is written in the message server being engaged in end；
The consumer client from least one the described message queue for being assigned to the consumer client by reading
The mode of the message data reads the message data from the message server in the server-side and is consumed.
2. message communication system as described in claim 1, which is characterized in that the message server includes that a message sink connects
Mouthful, the message sink interface message, and by the asynchronous persistent storage of the message received into a message logging；It is described
Message server includes the information query interface for Consumer System recalls information.
3. message communication system as described in claim 1, which is characterized in that the registration center specifically includes:
Storage unit includes the register list of online and successful registration the online equipment in the storage unit；
Monitoring unit connects the storage unit, for monitoring the online equipment in real time by the way of heartbeat monitor, and it is defeated
Real-time monitored results out；
Updating unit is separately connected the storage unit and the monitoring unit, for being judged whether according to the monitored results
There are the online equipment to have gone offline, and is updated according to judging result to the register list；
Notification unit is separately connected the updating unit and the storage unit, for updating institute every time in the updating unit
After stating register list, the updated register list is notified to each online equipment.
4. message communication system as claimed in claim 2, which is characterized in that the information query interface by pull mode to
Message server calls message data.
5. message communication system as described in claim 1, which is characterized in that the registration center is synchronous with the message subject
Message server is arrived into the number storage of corresponding message queue.
6. message communication system as described in claim 1, which is characterized in that the producer is by the way of poll, to extremely
Message server write-in institute of the mode of the message data into the server-side is written in a few message queue
State message data.
7. message communication system as claimed in claim 3, which is characterized in that the registration center further include:
Acquiring unit, for obtaining the message read requests of the consumer client, and according to the message read requests at
Reason obtains being associated with the quantity of the consumer client of each message subject；
Allocation unit connects the acquiring unit, and the allocation unit is directed to each message subject, described in needing to read
At least one not mutual duplicate described message queue of each of message subject consumer client's distribution.
8. message communication system as described in claim 1, which is characterized in that each message server respectively includes one and deposits
Space is stored up, multiple storage files are preserved in the memory space, the storage file and the message queue correspond, often
A storage file is respectively used to save data file pointed by the message data in the corresponding message queue.
9. message communication system as described in claim 1, which is characterized in that be respectively set one for each message subject
Retry queue；
The registration center further include:
Judging unit is read, for judging that the consumer client reads whether the message data succeeds, and output phase is answered
Judging result；
Unit is retried, the reading judging unit is connected, for the message count of failure will to be read according to the judging result
According to retrying in queue described in being put into corresponding to the message data, and the consumer client is allowed to retry team by described
Column read the message data.
10. message communication system as claimed in claim 9, which is characterized in that the registration center further include:
Counting unit, unit is retried described in connection, and the counting unit is retried for recording the consumer client from described
The number of the message data failure is read in queue；
When the number of counting unit record is more than a preset times, the unit that retries refuses the consumer client
Continue to read, and judge that this message data reads failure, then the message data is put into a dead letter queue.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810745624.4A CN109067844A (en) | 2018-07-09 | 2018-07-09 | A kind of message communication system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810745624.4A CN109067844A (en) | 2018-07-09 | 2018-07-09 | A kind of message communication system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109067844A true CN109067844A (en) | 2018-12-21 |
Family
ID=64819654
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810745624.4A Pending CN109067844A (en) | 2018-07-09 | 2018-07-09 | A kind of message communication system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109067844A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110300067A (en) * | 2019-06-26 | 2019-10-01 | 深圳前海微众银行股份有限公司 | Queue regulation method, device, equipment and computer readable storage medium |
| CN110413428A (en) * | 2019-08-06 | 2019-11-05 | 中国联合网络通信集团有限公司 | Processing method, electronic equipment and the storage medium of reconciliation data |
| CN110688228A (en) * | 2019-10-09 | 2020-01-14 | 北京思特奇信息技术股份有限公司 | Method, system and electronic equipment for guaranteeing distributed system message time sequence |
| CN112559208A (en) * | 2020-12-15 | 2021-03-26 | 浪潮云信息技术股份公司 | Method for constructing micro-service MQ applied to government affair cloud platform |
| CN112612959A (en) * | 2020-12-25 | 2021-04-06 | 深圳乐信软件技术有限公司 | Processing method, device, equipment and medium for push information |
| CN112631808A (en) * | 2020-12-29 | 2021-04-09 | 上海众源网络有限公司 | Data synchronization method and device, electronic equipment and storage medium |
| CN113590785A (en) * | 2021-07-29 | 2021-11-02 | 百度在线网络技术（北京）有限公司 | Message reply method and device, electronic equipment and storage medium |
| CN114979238A (en) * | 2022-05-24 | 2022-08-30 | 浪潮软件集团有限公司 | Multi-client data real-time pushing method and system |
| CN115695532A (en) * | 2023-01-04 | 2023-02-03 | 深圳竹云科技股份有限公司 | Method, device and computer equipment for processing message by message middleware |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040054886A1 (en) * | 1998-11-03 | 2004-03-18 | Dickinson Robert D. | E-mail firewall with stored key encryption/decryption |
| US20070130255A1 (en) * | 2003-04-17 | 2007-06-07 | Lionel Wolovitz | Data access, replication or communication system comprising a distributed software application |
| US20130066946A1 (en) * | 2011-09-09 | 2013-03-14 | Oracle International Corporation | System and method for providing a dynamic invocation and service interface for use in a middleware or other environment |
| CN104092767A (en) * | 2014-07-21 | 2014-10-08 | 北京邮电大学 | Posting/subscribing system for adding message queue models and working method thereof |
| CN105959349A (en) * | 2016-04-22 | 2016-09-21 | 上海瀚之友信息技术服务有限公司 | Distributed service end operation system and method |
| CN107197015A (en) * | 2017-05-23 | 2017-09-22 | 阿里巴巴集团控股有限公司 | A kind of message treatment method and device based on Message Queuing system |
| CN107370667A (en) * | 2017-07-31 | 2017-11-21 | 北京北信源软件股份有限公司 | Multi-threading parallel process method and apparatus, computer-readable recording medium and storage control |
| CN108255610A (en) * | 2018-01-12 | 2018-07-06 | 上海瀚银信息技术有限公司 | A kind of message broker Transmission system |
-
2018
- 2018-07-09 CN CN201810745624.4A patent/CN109067844A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040054886A1 (en) * | 1998-11-03 | 2004-03-18 | Dickinson Robert D. | E-mail firewall with stored key encryption/decryption |
| US20070130255A1 (en) * | 2003-04-17 | 2007-06-07 | Lionel Wolovitz | Data access, replication or communication system comprising a distributed software application |
| US20130066946A1 (en) * | 2011-09-09 | 2013-03-14 | Oracle International Corporation | System and method for providing a dynamic invocation and service interface for use in a middleware or other environment |
| CN104092767A (en) * | 2014-07-21 | 2014-10-08 | 北京邮电大学 | Posting/subscribing system for adding message queue models and working method thereof |
| CN105959349A (en) * | 2016-04-22 | 2016-09-21 | 上海瀚之友信息技术服务有限公司 | Distributed service end operation system and method |
| CN107197015A (en) * | 2017-05-23 | 2017-09-22 | 阿里巴巴集团控股有限公司 | A kind of message treatment method and device based on Message Queuing system |
| CN107370667A (en) * | 2017-07-31 | 2017-11-21 | 北京北信源软件股份有限公司 | Multi-threading parallel process method and apparatus, computer-readable recording medium and storage control |
| CN108255610A (en) * | 2018-01-12 | 2018-07-06 | 上海瀚银信息技术有限公司 | A kind of message broker Transmission system |
Non-Patent Citations (1)
| Title |
|---|
| 孙伟、郭宝龙: "《《嵌入式图像处理系统工程案例精选 DaVinci系统设计与实现》》", 30 April 2017 * |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110300067A (en) * | 2019-06-26 | 2019-10-01 | 深圳前海微众银行股份有限公司 | Queue regulation method, device, equipment and computer readable storage medium |
| CN110300067B (en) * | 2019-06-26 | 2022-02-08 | 深圳前海微众银行股份有限公司 | Queue adjusting method, device, equipment and computer readable storage medium |
| CN110413428A (en) * | 2019-08-06 | 2019-11-05 | 中国联合网络通信集团有限公司 | Processing method, electronic equipment and the storage medium of reconciliation data |
| CN110688228A (en) * | 2019-10-09 | 2020-01-14 | 北京思特奇信息技术股份有限公司 | Method, system and electronic equipment for guaranteeing distributed system message time sequence |
| CN112559208A (en) * | 2020-12-15 | 2021-03-26 | 浪潮云信息技术股份公司 | Method for constructing micro-service MQ applied to government affair cloud platform |
| CN112612959A (en) * | 2020-12-25 | 2021-04-06 | 深圳乐信软件技术有限公司 | Processing method, device, equipment and medium for push information |
| CN112612959B (en) * | 2020-12-25 | 2024-02-23 | 深圳乐信软件技术有限公司 | Push information processing method, device, equipment and medium |
| CN112631808A (en) * | 2020-12-29 | 2021-04-09 | 上海众源网络有限公司 | Data synchronization method and device, electronic equipment and storage medium |
| CN113590785A (en) * | 2021-07-29 | 2021-11-02 | 百度在线网络技术（北京）有限公司 | Message reply method and device, electronic equipment and storage medium |
| CN114979238A (en) * | 2022-05-24 | 2022-08-30 | 浪潮软件集团有限公司 | Multi-client data real-time pushing method and system |
| CN115695532A (en) * | 2023-01-04 | 2023-02-03 | 深圳竹云科技股份有限公司 | Method, device and computer equipment for processing message by message middleware |
| CN115695532B (en) * | 2023-01-04 | 2023-03-10 | 深圳竹云科技股份有限公司 | Method and device for processing message by message middleware and computer equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109067844A (en) | A kind of message communication system | |
| US7496579B2 (en) | Transitioning of database service responsibility responsive to server failure in a partially clustered computing environment | |
| US8856091B2 (en) | Method and apparatus for sequencing transactions globally in distributed database cluster | |
| US9785691B2 (en) | Method and apparatus for sequencing transactions globally in a distributed database cluster | |
| US7219103B2 (en) | System and method for data replication in a computer system | |
| US20210112013A1 (en) | Message broker system with parallel persistence | |
| US8108352B1 (en) | Data store replication for entity based partition | |
| CN108712457B (en) | Method and device for adjusting dynamic load of back-end server based on Nginx reverse proxy | |
| US9141435B2 (en) | System and methodology providing workload management in database cluster | |
| JP3320985B2 (en) | Node selecting method, distributed video server system, storage selecting method, and distributed computing system | |
| US5687372A (en) | Customer information control system and method in a loosely coupled parallel processing environment | |
| US10331625B2 (en) | Managing sequential data store | |
| EP2555129A1 (en) | Method and system to maintain strong consistency of distributed replicated contents in a client/server system | |
| US20020131423A1 (en) | Method and apparatus for real-time parallel delivery of segments of a large payload file | |
| US20150317371A1 (en) | Method, device, and system for peer-to-peer data replication and method, device, and system for master node switching | |
| US5682507A (en) | Plurality of servers having identical customer information control procedure functions using temporary storage file of a predetermined server for centrally storing temporary data records | |
| US6347322B1 (en) | Transaction state data replication by transaction forwarding in replicated database systems | |
| JP2013065120A (en) | Load distribution system, data access device, and load distribution method | |
| EP0747812A2 (en) | Customer information control system and method with API start and cancel transaction functions in a loosely coupled parallel processing environment | |
| CN107180034A (en) | The group system of MySQL database | |
| CN110880986A (en) | High-availability NAS storage system based on Ceph | |
| US12019873B2 (en) | Methods and systems to improve resumption time of input/output (I/O) operations based on prefetching of configuration data and early abort of conflicting workflows during a non-disruptive automatic unplanned failover from a primary copy of data at a primary storage system to a mirror copy of the data at a cross-site secondary storage system | |
| US20230185631A1 (en) | Embedded capacity-computer module for microservice load balancing and distribution | |
| Pankowski | Consistency and availability of Data in replicated NoSQL databases | |
| CN113742336A (en) | Data processing method and device and storage medium |
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 |