CN108255610A - A kind of message broker Transmission system - Google Patents
A kind of message broker Transmission system Download PDFInfo
- Publication number
- CN108255610A CN108255610A CN201810031683.5A CN201810031683A CN108255610A CN 108255610 A CN108255610 A CN 108255610A CN 201810031683 A CN201810031683 A CN 201810031683A CN 108255610 A CN108255610 A CN 108255610A
- Authority
- CN
- China
- Prior art keywords
- message
- storage
- transmission system
- file
- message broker
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
-
- 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/2866—Architectures; Arrangements
- H04L67/2871—Implementation details of single intermediate entities
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a kind of message broker Transmission systems, belong to message-oriented middleware technical field;Message broker Transmission system is remotely connect with multiple client, and message is transmitted by message broker Transmission system between multiple client;Message broker Transmission system specifically includes:Storage unit, for preserving message;In including multiple storage files in storage unit, message is stored in respectively in each storage file;In further including an index file in storage unit, index file includes the offset that each message is saved in storage file;The position that client is saved by index file localization message, and then obtain the message being stored in storage unit.The advantageous effect of above-mentioned technical proposal is:It solves the problems, such as that message queue is crowded, effectively reduces the loss of file resource, I/O resources and memory source, and can complete to low latency the Run-time scenario of high concurrent and mass data and there is ability extending transversely.
Description
Technical field
The present invention relates to message-oriented middleware technical field more particularly to a kind of message broker Transmission systems.
Background technology
With the increasingly prosperity of mechanics of communication, the message intercommunication between is generally required through message-oriented middleware come real
It is existing.Message-oriented middleware can carry out platform-independent data exchange using the message passing mechanism of high efficient and reliable, and based on data
It communicates to carry out the integrated of distributed system.By providing message transmission and message queueing model, it can be in distributed environment
Communication between lower extension process.
Traditional message-oriented middleware is typically the mediating transmission that message is carried out using message queue, among this message
Part can not handle the transmission of a large amount of message under the application environment of mass data, can cause the blocking of message queue.Also, based on mesh
The application environment of preceding big data quantity, traditional message-oriented middleware can cause higher file resource, I/O resources in the process of running
And the loss of memory source etc., so as to cause the decline of Message Processing efficiency, the delay that message is caused to be transmitted, user's should
It can also be declined therewith with experience.
Invention content
According to the above-mentioned problems in the prior art, a kind of technical solution of message broker Transmission system, purport are now provided
It is solving the problems, such as that message queue is crowded, is effectively reducing the loss of file resource, I/O resources and memory source, and can be low
Lingeringly complete the Run-time scenario of high concurrent and mass data and with ability extending transversely.
Above-mentioned technical proposal specifically includes:
A kind of message broker Transmission system, wherein, the message broker Transmission system is remotely connect with multiple client, more
Message is transmitted by the message broker Transmission system between a client;
The message broker Transmission system specifically includes:
Storage unit, for preserving the message;
In including multiple storage files in the storage unit, the message is stored in each storage file respectively
In;
In further including an index file in the storage unit, the index file includes each message and is saved
Offset in the storage file;
The client positions the position that the message is saved by the index file, so obtain be stored in it is described
The message in storage unit.
Preferably, the message broker Transmission system, wherein, multiple clients include:
Multiple production clients, each production client are respectively used to generate the message and to the message brokers
Transmission system is transmitted;
Multiple customer ends, each customer end are respectively used to through the index file actively extraction preservation
The message in the storage unit is simultaneously consumed;
The customer end is additionally operable to manage the consumption status of the message, and the consumption status is supplied to described
Message broker Transmission system.
Preferably, the message broker Transmission system, wherein, it is further included in the message broker Transmission system:
Message storage connects the storage unit, preserves the message to described for passing through kernel thread and deposits
In storage unit;
Message handling unit connects the message storage, obtains the message for passing through user thread and will obtain
The message got is carried in the message storage;
After the message storage all preserves the message being handled upside down to the storage unit, the message
Storage unit sends an asynchronous notifications to the message handling unit, the message handling unit to be notified to continue to the message
The message is carried in storage unit.
Preferably, the message broker Transmission system, wherein, the storage file is journal file;
A line of the journal file is for one message of expression.
Preferably, the message broker Transmission system, wherein, 8 storage files are included at least in the storage unit.
Preferably, the message broker Transmission system, wherein, the storage unit includes multiple memory modules, Mei Gesuo
It states and the part storage file is preserved in memory module, each memory module is respectively set at different data storages
In server;
It is further included in the message broker Transmission system:
First control unit, connects the storage unit, and first control unit is used for each memory module
Heartbeat detection is carried out, to judge whether the memory module survives, first control unit is corresponding to the client feedback
Judging result;
First control unit is arranged in data control server.
Preferably, the message broker Transmission system, wherein, the data control server and all data storage clothes
Business device is arranged in same server cluster.
Preferably, the message broker Transmission system, wherein, multiple clients include:
Multiple production clients, each production client are respectively used to generate the message and to the message brokers
Transmission system is transmitted;
Multiple customer ends, each customer end are respectively used to through the index file actively extraction preservation
The message in the storage unit is simultaneously consumed;
In synchronization, a storage file is only supplied to the behaviour of a customer end progress message acquisition
Make;
The message broker Transmission system further includes:
Second control unit, connects the storage unit, and second control unit is literary for monitoring each storage
The current of part obtains state, and the storage file that continuous updating is currently available;
Before the customer end obtains the message from the message broker Transmission system, first to the described second control
Unit processed is registered, to know the currently available storage file;
Second control unit is arranged in the data control server.
Preferably, the message broker Transmission system, wherein, each storage mould is further included in second control unit
The routing iinformation of block;
Know currently available storage text when being registered to second control unit in the customer end
The routing iinformation of the memory module where part.
Preferably, the message broker Transmission system, wherein, distributed deployment is supported at multiple customer ends;And/or
Multiple production clients support distributed deployment.
The advantageous effect of above-mentioned technical proposal is:A kind of message broker Transmission system is provided, message queue can be solved and gathered around
The problem of squeezing, effectively reduces the loss of file resource, I/O resources and memory source, and can complete high concurrent to low latency
With the Run-time scenario of mass data and with ability extending transversely.
Description of the drawings
Fig. 1 is a kind of general structure schematic diagram of message broker Transmission system in the preferred embodiment of the present invention.
Specific embodiment
Below in conjunction with the attached drawing in the embodiment of the present invention, the technical solution in the embodiment of the present invention is carried out clear, complete
Site preparation describes, it is clear that described embodiment is only part of the embodiment 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 obtained under the premise of creative work is not made 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 invention will be further described in the following with reference to the drawings and specific embodiments, but not as limiting to the invention.
According to the above-mentioned problems in the prior art, a kind of message broker Transmission system is now provided, as shown in fig. 1,
Message broker Transmission system A connects multiple client respectively, is disappeared between client by message broker Transmission system A realizations
The intercommunication of breath.
Specifically, message broker Transmission system A includes:
Storage unit A 1, for preserving message;
In including multiple storage files in storage unit A 1, message is stored in respectively in each storage file;
In further including an index file in storage unit A 1, index file includes each message and is saved in storage file
In offset;
The position that client is saved by index file localization message, and then obtain and be stored in disappearing in storage unit A 1
Breath.
In the present embodiment, message-oriented middleware of the above-mentioned message broker Transmission system as transmission message between client, when
It needs to transmit in message mutually between application program in client, client carries out message by message broker Transmission system
Intercommunication.
For example, this message intercommunication is related to two clients, one of client generates message and uploads message
It is preserved into the storage unit A 1 of message broker Transmission system A, another client is from the storage list of message broker Transmission system A
Corresponding message is actively extracted in first A1 and is consumed.In other words, in the application, A is for message for message broker Transmission system
Transmission be to be carried out by the way of " push-and-pull ", that is, message " pushing away " to message broker is transmitted and is by the client for generating message
It is preserved in system A, consuming the client of message, from message broker Transmission system A " drawings " out and is consumed by message, all
The process of message transmission is dominated by client, this is needed actively with conventional message middleware to the characteristic of client push message
It is entirely different, while this mechanism can also be supplied to the more flexibility ratios of client.
In the present embodiment, in the message in Jie's Transmission system A, multiple storage files are provided in storage unit A 1, each
Storage file is used to preserve message.In other words, it is different more in the preserving type of storage unit A 1 to be that cycle is stored in for message
In a storage file.And for client, what message broker Transmission system was supplied to client is still a message team
Row, the above-mentioned practical bottom for being arranged on system of multiple storage files.
In the present embodiment, another file is additionally provided in said memory cells A1, this document is an index text
Part, wherein record has each message to be saved in the offset in storage file (offset).Therefore, client can be by this
The storage file and its corresponding storage location that the message that index file positioning needs obtain is preserved, needed for smoothly obtaining
The message wanted.Doing so can realize that data are detached with the storage indexed, only by index file in face of client, therefore can have
Effect reduces the loss of file resource, I/O resources and memory source.
In the present embodiment, between above-mentioned message broker Transmission system A and client using Netty exploitation communication interface into
The communication of row message.
Further, in preferred embodiment of the invention, still as shown in fig. 1, above-mentioned multiple client includes:
Multiple production customer end Bs 1, each customer end B 1 that produces are respectively used to generate message and to message broker Transmission system
A is transmitted;
Multiple customer end B2, each customer end B2 are respectively used to actively extract to be stored in by index file to deposit
Message in storage unit A1 is simultaneously consumed;
Customer end B2 is additionally operable to the consumption status of management message, and consumption status is supplied to message broker transmission system
Unite A.
Specifically, in the present embodiment, production customer end B 1 is to generate the client of message, and production customer end B 1 is responsible for generation
Message and message is pushed in message broker Transmission system A preserves.
In the present embodiment, customer end B2 is the client for consuming message, and customer end B2 is responsible for from message broker
Message is obtained in Transmission system A and is consumed.Customer end B2 occupies leading position, i.e. customer end in this process
B2 actively extracts message from message broker Transmission system A and is consumed rather than from message broker Transmission system A to consumption
2 PUSH message of customer end B.
In addition, in the present embodiment, since customer end B2 occupies leading position during information consumption,
Should the consumption status whether message is consumed be managed by customer end B2.In other words, when B2 extractions in customer end disappear
After ceasing and consuming, the consumption status of the message is managed by customer end B2, and the consumption status is fed back into message broker
In Transmission system A.Message broker Transmission system A is operated accordingly according to the consumption status of feedback come the message to preservation.
Such as the current state of message finished from message broker Transmission system A is deleted or will be consumed to the message for finishing consumption
" consumption " is changed to, so as to which the message be prevented to be repeated extraction etc..
In the preferred embodiment of the present invention, still as shown in fig. 1, further included in above-mentioned message broker Transmission system A:
Message storage A2 connects storage unit A 1, preserves message into storage unit for passing through kernel thread;
Message handling unit A3, connection message storage unit A 2, for obtaining message by user thread and will get
Message be carried in message storage A2;
When message storage A2 by the message being handled upside down all preserve to storage unit A 1 after, message storage A2 to
Message handling unit A3 sends an asynchronous notifications, continues to carry into message storage with notification message handling unit A3 and disappears
Breath.
Specifically, in the present embodiment, above-mentioned message storage A2 is worked by the kernel thread of system, above-mentioned to disappear
Breath handling unit A3 is worked by the user thread of system, and user thread and kernel thread are mutual asynchronous executions.
In the prior art, message-oriented middleware is usually all to carry out the storage of message by user thread and transfer,
In the case of a large amount of message are to be treated, user thread can be in busy state at the moment, so as to which thread is caused to block, and
And affect the efficiency that user thread handles other tasks.
And in the application, the storing process of message is jointly processed by using asynchronous user thread and kernel thread, it can be with
Avoid excessively occupying the resource of user thread.Specifically, user thread will need the message stored to be sent into after kernel thread just
It can be released and handle other tasks.Disappeared again by asynchronous after kernel thread is by message all deposit storage unit A 1
Breath notice user thread conveys message to kernel thread.
In the preferred embodiment of the present invention, above-mentioned storage file is journal file, and a line of journal file is i.e. for table
Show a piece of news.
In the preferred embodiment of the present invention, 8 storage files are included at least in said memory cells, message is protected by cycle
There are at least eight storage file, for client call.
In the preferred embodiment of the present invention, still as shown in fig. 1, said memory cells A1 includes multiple storage moulds
Part storage file is preserved in block A11, each memory module A11, each memory module A11 is respectively set at different numbers
According in storage server A4;
It is further included in message broker Transmission system A:
First control unit A5, connects storage unit A 1, and the first control unit A5 is used to carry out each memory module A11
Heartbeat detection, to judge whether memory module A11 survives, the first control unit A5 to client (be in particular customer end
B2 corresponding judging result) is fed back;
First control unit A5 is arranged in data control server A 6.
As shown in fig. 1, above-mentioned message handling unit A2 and message storage A3 is equally arranged on data control clothes
It is engaged in device A6.
Specifically, in the present embodiment, said memory cells A1 is actually made of multiple data storage server A4, and logarithm
The functional unit controlled according to storage server A4 (such as deposit by the first control unit A5, message handling unit A2 and message
Storage unit A3) it is included in a data control server A 6, data control server A 6 connects each data respectively
Storage server.
In the present embodiment, above-mentioned first control unit A5 is used to carry out heartbeat detection (namely to each memory module A11
Heartbeat detection is carried out to each data storage server A4), to determine whether each memory module A11 survives.Heartbeat detection
Detailed process may be used mode of the prior art and realize, such as the first control unit A5 storage and maintenance one are movable
" data storage server list " includes the data storage server of current activity in the list.First control unit A5 weeks
Heartbeat detection signal is sent, and pass through whether data storage server A4 has feedback to each data storage server A4 to phase property
To judge whether data storage server A4 survives.First control unit A5 then safeguards that above-mentioned data are deposited according to judging result
Server list is stored up, the data storage server A4 for being wherein judged as not surviving is deleted from the list.First control is single
First A5 is simultaneously by above-mentioned data storage server list synchronization to feeding back in customer end B2 and production customer end B 1, to refer to
Show that customer end B2 obtains message from the data storage server A4 survived at present.Therefore the above " the first control
Unit A5 processed is to the corresponding judging result of client feedback " refer to the first control terminal A5 and pass through to customer end B2 and production visitor
The mode that family end B1 synchronizes above-mentioned data storage server list informs that customer end B2 and production customer end B 1 are currently survived
Data storage server.
In the present embodiment, in order to realize that " push-and-pull " of data is transmitted, included in above-mentioned each data storage server A4
The data storage configuration of the message preserved, and it controls server A 6 to receive customer end B2 and production by data
The registration request of customer end B 1, and safeguard and preserve the row for the customer end B2 for being currently accessing data storage server A4
Table and the list for producing customer end B 1.(stop the heart when customer end B2 or production customer end B 1 stop registration request
Jump) after, it is deleted from corresponding list.Further, above-mentioned data storage server A4 also needs to handle and storage disappears
The message of expense customer end B 2 pulls longitude, to realize the breakpoint transmission of message.Meanwhile data storage server A4 can be handled and be disappeared
Take customer end B 2 controls the inquiry request of the transmission of server A 6 and process for producing customer end B 1 to be controlled by data by data
Message storage request that server A 6 is sent etc..
Further, in preferred embodiment of the invention, above-mentioned data storage server A4 and data control server
A6 is in together in a server cluster, in order to which data control server A 6 is monitored and controls to data storage server A4
System.
In the preferred embodiment of the present invention, in synchronization, a storage file is only supplied to a customer end
Carry out the operation of message acquisition;
Then still as shown in fig. 1, above-mentioned message broker Transmission system A is further included:
Second control unit A7, connects storage unit A 1, and the second control unit A7 is used to monitor working as each storage file
Preceding acquisition state, and the storage file that continuous updating is currently available;
Before customer end B1 obtains message from message broker Transmission system, first noted to the second control unit
Volume, to know currently available storage file;
Second control unit A7 is arranged in data control server A 6.
Conflict is generated when specifically, in order to avoid reading message, defines one storage of synchronization in the present embodiment
The considerations of file is only available to a customer end B2 to access, this is also in load balancing.On this basis, lead to
One second control unit A7 is crossed to be monitored to the storage file in storage unit A 1, and feeds back working as different storage files
Preceding acquisition state.Specifically, so-called current acquisition state can include two kinds, one kind be storage file be currently unavailable (i.e. should
Storage file currently just by some customer end B2 access), another kind be storage file it is currently available (i.e. the storage file ought
It is preceding not accessed by any one customer end B2).
In order to monitor the current acquisition state of storage file, in the application by way of customer end B2 registrations come into
Row.Specifically, if customer end B2 wants to obtain message by message broker Transmission system, customer end B2 needs head
First registered to the second control unit A7 and form a log-on message in the second control unit A7.It is specific in the log-on message
Including:Storage file that client id and the customer end B2 needs of customer end B2 access etc..Second control
Unit A7 determines storage file that customer end B2 will be accessed, and to the current of the storage file according to the log-on message
Acquisition state is modified.Correspondingly, the second control unit A7 can continue to feed back each storage file to customer end B2
It is current to obtain state, so that customer end B2 is selected in registration.For example, for 8 storages in storage unit A 1
File, the log-on message of customer end B2s of the second control unit A7 before determine the storage being currently accessed text
Part is 2-5 storage files, and the current acquisition state of 2-5 storage files is changed to currently by the second control unit A7 at this time
Unavailable, subsequent customer end B2 can only be assigned when being registered using the 1st, 6-8 storage files.Further
Ground, for proof load equilibrium, when needing to obtain message simultaneously for subsequent multiple customer end B2, the second control unit
A7 is distributed equally or notifies each consumption in the range of currently available storage file to each customer end B2
Customer end B 2 is distributed equally as far as possible through consultation.The sum of customer end B2 disappears no more than what current needs pulled
The quantity of the corresponding storage file of breath.For example, when storage file only has 8, the customer end B2 that can be read
At most can only also there are 8.
Further, in preferred embodiment of the invention, above-mentioned data control server A 6 cuts out device in being one.
In the preferred embodiment of the present invention, the road of each memory module A11 is further included in above-mentioned second control unit A7
By information;
Customer end B2 to the second control unit A7 when being registered, where knowing currently available storage file
The routing iinformation of memory module A11, so as to position and access the position where memory module A11.
In the preferred embodiment of the present invention, multiple customer end B2 support distributed deployment.
In the preferred embodiment of the present invention, multiple production customer end Bs 1 support distributed deployment.
The foregoing is merely preferred embodiments of the present invention, not thereby 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 include within the scope of the present invention.
Claims (10)
1. a kind of message broker Transmission system, which is characterized in that the message broker Transmission system remotely connects with multiple client
It connects, message is transmitted by the message broker Transmission system between multiple client;
The message broker Transmission system specifically includes:
Storage unit, for preserving the message;
In including multiple storage files in the storage unit, the message is stored in respectively in each storage file;
In further including an index file in the storage unit, the index file includes each message and is saved in institute
State the offset in storage file;
The position that the client is saved by the index file positioning message, and then obtain and be stored in the storage
The message in unit.
2. message broker Transmission system as described in claim 1, which is characterized in that multiple clients include:
Multiple production clients, each production client are respectively used to generate the message and be transmitted to the message broker
System is transmitted;
Multiple customer ends, each customer end, which is respectively used to actively extract by the index file, is stored in institute
It states the message in storage unit and is consumed;
The customer end is additionally operable to manage the consumption status of the message, and the consumption status is supplied to the message
Mediating transmission system.
3. message broker Transmission system as described in claim 1, which is characterized in that also wrapped in the message broker Transmission system
It includes:
Message storage connects the storage unit, preserves the message to the storage list for passing through kernel thread
In member;
Message handling unit connects the message storage, obtains the message for passing through user thread and will get
The message be carried in the message storage;
After the message storage all preserves the message being handled upside down to the storage unit, the message storage
Unit sends an asynchronous notifications to the message handling unit, the message handling unit to be notified to continue to store to the message
The message is carried in unit.
4. message broker Transmission system as described in claim 1, which is characterized in that the storage file is journal file;
A line of the journal file is for one message of expression.
5. message broker Transmission system as described in claim 1, which is characterized in that 8 are included at least in the storage unit
The storage file.
6. message broker Transmission system as described in claim 1, which is characterized in that the storage unit includes multiple storages
Module each preserves the part storage file in the memory module, and each memory module is respectively set at not
In same data storage server;
It is further included in the message broker Transmission system:
First control unit, connects the storage unit, and first control unit is used to carry out each memory module
Heartbeat detection, to judge whether the memory module survives, first control unit is sentenced accordingly to the client feedback
Disconnected result;
First control unit is arranged in data control server.
7. message broker Transmission system as claimed in claim 6, which is characterized in that the data control server and all institutes
Data storage server is stated to be arranged in same server cluster.
8. message broker Transmission system as claimed in claim 6, which is characterized in that multiple clients include:
Multiple production clients, each production client are respectively used to generate the message and be transmitted to the message broker
System is transmitted;
Multiple customer ends, each customer end, which is respectively used to actively extract by the index file, is stored in institute
It states the message in storage unit and is consumed;
In synchronization, a storage file is only supplied to the operation of a customer end progress message acquisition;
The message broker Transmission system further includes:
Second control unit, connects the storage unit, and second control unit is used to monitor each storage file
It is current to obtain state, and the storage file that continuous updating is currently available;
It is first single to the described second control before the customer end obtains the message from the message broker Transmission system
Member is registered, to know the currently available storage file;
Second control unit is arranged in the data control server.
9. message broker Transmission system as claimed in claim 8, which is characterized in that further included in second control unit every
The routing iinformation of a memory module;
Know the currently available storage file institute when being registered to second control unit in the customer end
The memory module the routing iinformation.
10. message broker Transmission system as claimed in claim 2, which is characterized in that support to divide in multiple customer ends
Cloth is disposed;And/or
Multiple production clients support distributed deployment.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810031683.5A CN108255610A (en) | 2018-01-12 | 2018-01-12 | A kind of message broker Transmission system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810031683.5A CN108255610A (en) | 2018-01-12 | 2018-01-12 | A kind of message broker Transmission system |
Publications (1)
Publication Number | Publication Date |
---|---|
CN108255610A true CN108255610A (en) | 2018-07-06 |
Family
ID=62727274
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201810031683.5A Pending CN108255610A (en) | 2018-01-12 | 2018-01-12 | A kind of message broker Transmission system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN108255610A (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109067844A (en) * | 2018-07-09 | 2018-12-21 | 上海瀚银信息技术有限公司 | A kind of message communication system |
CN109743137A (en) * | 2019-01-10 | 2019-05-10 | 浙江小泰科技有限公司 | A kind of Distributed Delay message queue processing system for supporting to update |
CN111381983A (en) * | 2020-03-06 | 2020-07-07 | 西安理工大学 | Lightweight message middleware system and method of virtual test target range verification system |
CN112087501A (en) * | 2020-08-28 | 2020-12-15 | 北京明略昭辉科技有限公司 | Transmission method and system for keeping data consistency |
CN113159858A (en) * | 2021-05-06 | 2021-07-23 | 山东白令三维科技有限公司 | 3D printing quotation system, method and device and storage medium |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120272252A1 (en) * | 2011-04-20 | 2012-10-25 | International Business Machines Corporation | Monitoring of subscriber message processing in a publish/subscribe messaging environment |
CN104092767A (en) * | 2014-07-21 | 2014-10-08 | 北京邮电大学 | Posting/subscribing system for adding message queue models and working method thereof |
CN106953901A (en) * | 2017-03-10 | 2017-07-14 | 重庆邮电大学 | A kind of trunked communication system and its method for improving message transmission performance |
-
2018
- 2018-01-12 CN CN201810031683.5A patent/CN108255610A/en active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120272252A1 (en) * | 2011-04-20 | 2012-10-25 | International Business Machines Corporation | Monitoring of subscriber message processing in a publish/subscribe messaging environment |
CN104092767A (en) * | 2014-07-21 | 2014-10-08 | 北京邮电大学 | Posting/subscribing system for adding message queue models and working method thereof |
CN106953901A (en) * | 2017-03-10 | 2017-07-14 | 重庆邮电大学 | A kind of trunked communication system and its method for improving message transmission performance |
Non-Patent Citations (4)
Title |
---|
GERO MUHL: "Analyzing content=based publish/subscribe systems", 《PROCEEDINGS OF THE 9TH ACM INTERNATIONAL CONFERENCE ON DISTRIBUTED EVENT-BASED SYSTEMS》 * |
牟大恩: "《Kafka入门与实践》", 30 November 2017 * |
肖冠宇: "《企业大数据处理Spark、Druid、Flume与Kafka应用实践》", 30 September 2017 * |
马浩然: "基于NS3的分布式消息系统Kafka的仿真实现", 《中国优秀硕士学位论文全文数据库信息科技辑》 * |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109067844A (en) * | 2018-07-09 | 2018-12-21 | 上海瀚银信息技术有限公司 | A kind of message communication system |
CN109743137A (en) * | 2019-01-10 | 2019-05-10 | 浙江小泰科技有限公司 | A kind of Distributed Delay message queue processing system for supporting to update |
CN109743137B (en) * | 2019-01-10 | 2022-01-14 | 浙江小泰科技有限公司 | Distributed delay message queue processing system supporting updating |
CN111381983A (en) * | 2020-03-06 | 2020-07-07 | 西安理工大学 | Lightweight message middleware system and method of virtual test target range verification system |
CN111381983B (en) * | 2020-03-06 | 2022-09-20 | 西安理工大学 | Lightweight message middleware system and method of virtual test target range verification system |
CN112087501A (en) * | 2020-08-28 | 2020-12-15 | 北京明略昭辉科技有限公司 | Transmission method and system for keeping data consistency |
CN112087501B (en) * | 2020-08-28 | 2023-10-24 | 北京明略昭辉科技有限公司 | Transmission method and system for maintaining data consistency |
CN113159858A (en) * | 2021-05-06 | 2021-07-23 | 山东白令三维科技有限公司 | 3D printing quotation system, method and device and storage medium |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN108255610A (en) | A kind of message broker Transmission system | |
US8898680B2 (en) | System and method for supporting asynchronous message processing in a distributed data grid | |
US9703610B2 (en) | Extensible centralized dynamic resource distribution in a clustered data grid | |
CN101207550B (en) | Load balancing system and method for multi business to implement load balancing | |
CN103237046B (en) | Support distributed file system and the implementation method of mixed cloud storage application | |
US6463465B1 (en) | System for facilitating remote access to parallel file system in a network using priviliged kernel mode and unpriviliged user mode to avoid processing failure | |
CN108885582A (en) | The multi-tenant memory services of memory pool structure | |
CN104754036A (en) | Message processing system and processing method based on kafka | |
US20090300169A1 (en) | Synchronization throttling based on user activity | |
US6430616B1 (en) | Scalable system method for efficiently logging management information associated with a network | |
CN105610947A (en) | Method, device and system for realizing high-available distributed queue service | |
CN106656846A (en) | Construction method of coordination layer in software defined network (SDN) architecture | |
CN108228393A (en) | A kind of implementation method of expansible big data High Availabitity | |
CN109074287A (en) | Infrastructure resources state | |
CN108664520A (en) | Safeguard method, apparatus, electronic equipment and the readable storage medium storing program for executing of data consistency | |
CN107197039B (en) | A kind of PAAS platform service packet distribution method and system based on CDN | |
WO2020117542A1 (en) | Object oriented call management | |
CN108595121B (en) | Data storage method and device | |
CN113574515A (en) | Asynchronous storage management in distributed systems | |
US20150244782A1 (en) | Server for distributed controller system | |
CN107370797A (en) | A kind of method and apparatus of the strongly-ordered queue operation based on HBase | |
CN116775420A (en) | Information creation cloud platform resource display and early warning method and system based on Flink flow calculation | |
CN113472864B (en) | High-performance block chain distributed storage system, method, equipment and storage medium | |
CN108076111B (en) | System and method for distributing data in big data platform | |
CN114598662A (en) | Message queue cluster federal management system and method |
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: 20180706 |
|
RJ01 | Rejection of invention patent application after publication |