CN109451032A - A kind of messaging system - Google Patents
A kind of messaging system Download PDFInfo
- Publication number
- CN109451032A CN109451032A CN201811386086.0A CN201811386086A CN109451032A CN 109451032 A CN109451032 A CN 109451032A CN 201811386086 A CN201811386086 A CN 201811386086A CN 109451032 A CN109451032 A CN 109451032A
- Authority
- CN
- China
- Prior art keywords
- message
- desk
- transmission
- sent
- sending
- 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.)
- Granted
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/562—Brokering proxy services
-
- 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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- 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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/62—Establishing a time schedule for servicing the requests
Abstract
The invention discloses a kind of messaging systems, it include: message desk, database and message-oriented middleware, the message desk is connect with message subscribing end and message sending end respectively, the message desk is also connect with the database and the message-oriented middleware respectively, the message sending end is sent to the message desk for that will send request, the message desk is based on transmission request and generates transmission message, and according to the timing for sending request, by corresponding transmission message storage to database, and the transmission message is sent to the message-oriented middleware, request is subscribed to the message desk for sending in the message subscribing end, compared with traditional message transferring technology, technical solution of the present invention is completed to send the storage and transmission of message based on the timing for sending request, avoid the loss of message in transmission process, guarantee The integrality and consistency of message, improves the performance of system.
Description
Technical field
The present embodiments relate to data communication technology field more particularly to a kind of messaging systems.
Background technique
Traditional message transmission can only send a message to receiving terminal from application end, when receiving terminal delay machine or occur mistake and
No longer received message when, will cause the loss of message.Message-oriented middleware can be used in order to avoid this kind of situation
(Message Oriented Middleware, MOM), message-oriented middleware can communicate between different platform, often be used to shield
It covers the characteristic between various platforms and agreement, realizes the collaboration between application program.
Traditional message-oriented middleware mostly uses greatly the transmitting of synchronization call completion message, and synchronization call needs system synchronous
A large number of services logic is handled, causing user to request, slow, experience is poor, and the meeting when system receives the request from a large number of users
Huge pressure is brought to whole system, in some instances it may even be possible to cause to service delay machine or whole system paralysis.In addition, Large-Scale Interconnected net point
There are multiple services for cloth system, and according to this traditional message-oriented middleware, each service requires to provide the producer and disappear
Fei Zhe, it is extremely complex cumbersome that this allows for entire distributed system.
Summary of the invention
The embodiment of the present invention provides a kind of messaging system, and the storage for sending message is completed based on the timing for sending request
With transmission, the loss of message in transmission process is avoided, guarantees the integrality and consistency of message, improves the performance of system.
The embodiment of the present invention provides a kind of messaging system, comprising: message desk, database and message-oriented middleware；
The message desk is connect with message subscribing end and message sending end respectively, the message desk also respectively with it is described
Database is connected with the message-oriented middleware,
The message sending end is sent to the message desk for that will send request, and the message desk is based on the hair
It send to request to generate and sends message, and according to the timing for sending request, corresponding transmission message is stored to the database,
And the transmission message is sent to the message-oriented middleware, request is subscribed to the message for sending in the message subscribing end
Platform.
Further, the transmission packet includes transaction message and non-transactional message, correspondingly,
When the transmission message is transaction message, the message desk is used for the hair after message sending end confirmation
Message is sent to be sent to the message-oriented middleware；
When the transmission message is non-transactional message, the message desk is for the transmission message to be transmitted directly to
The message-oriented middleware.
Further, the message desk is also used to receive the subscription request that the message subscribing end is sent, and to described
Request is subscribed to be parsed.
Further, the message-oriented middleware, which is also used to send, subscribes to message to the message desk, the subscription message
For the message corresponding with parsing result stored in the message-oriented middleware.
Further, the message desk is also used to the subscription message being sent to the message subscribing end.
Further, the message desk is also used to when the transmission message for being sent to the message-oriented middleware or is sent to institute
When stating the subscription message at message subscribing end and sending failure, according to preset message retry strategy retransmit the transmission message or
The subscription message.
Further, the message desk is also used to carry out power to the transmission message according to the number for sending message
Deng processing.
Further, the message desk is also used to carry out power to the subscription message according to the number for subscribing to message
Deng processing.
The embodiment of the present invention provides a kind of messaging system, comprising: message desk, database and message-oriented middleware, institute
Message desk is stated to connect with message subscribing end and message sending end respectively, the message desk also respectively with the database and institute
Message-oriented middleware connection is stated, the message sending end is sent to the message desk, the message desk for that will send request
Based on the transmission request generate send message, and according to it is described send request timing, by corresponding transmission message storage to
The database, and the transmission message is sent to the message-oriented middleware, the message subscribing end is asked for sending to subscribe to
It asks to the message desk, compared with traditional message transferring technology, technical solution of the present invention is based on the timing for sending request
The storage and transmission for completing to send message, avoid the loss of message in transmission process, ensure that the integrality of message with it is consistent
Property, improve the performance of system.
Detailed description of the invention
Fig. 1 is a kind of structure chart of messaging system provided in an embodiment of the present invention；
Fig. 2 is the time diagram that transaction message executes；
Fig. 3 is the time diagram that non-transactional message executes.
Specific embodiment
The present invention is described in further detail with reference to the accompanying drawings and examples.It is understood that this place is retouched
The specific embodiment stated is used only for explaining the present invention rather than limiting the invention.It also should be noted that in order to just
Only the parts related to the present invention are shown in description, attached drawing rather than entire infrastructure.
Fig. 1 is a kind of structure chart of messaging system provided in an embodiment of the present invention, and the present embodiment is applicable to be distributed
The case where formula system data transmission, specifically, the system includes: message desk 110, database 120 and message-oriented middleware 130；
Message desk 110 is connect with message subscribing end 150 and message sending end 140 respectively, message desk 110 also respectively with
Database 120 and message-oriented middleware 130 connect,
Message sending end 140 is sent to message desk 110 for that will send request, and message desk 110 is based on sending request
It generates and sends message, and according to the timing for sending request, corresponding transmission message is stored to database 120, and by transmission and is disappeared
Breath is sent to message-oriented middleware 130, and request is subscribed to message desk 110 for sending in message subscribing end 150.
Specifically, 110 one side of message desk can receive the transmission request of the transmission of message sending end 140, and will be with hair
It send the corresponding transmission message of request to be sent to message-oriented middleware 120, on the other hand can also receive the transmission of message subscribing end 150
Request is subscribed to, subscription message corresponding with subscription request is sent to message subscribing end 150, i.e., message desk 110 both can be with
As the producer of message, and it can be used as the consumer of message, wherein the producer of message is that message desk 110 receives hair
After sending request, which can be requested to pack, generate corresponding transmission message.Specifically, sending request can be packet
Containing the content for sending message and desired request is sent, when the transmission request comprising content is sent to by message sending end 140
After message desk 110, message desk 110 requires to pack to generate and send out the received content for sending message according to transmission
It send and requires corresponding transmission message.The consumer of message is that message desk 110 sends subscription message to message subscribing end 150, tool
Body, after message desk 110 receives the subscription request that message subscribing end 150 is sent, obtain subscription relevant to subscription request
Message, and the subscription message is sent to message subscribing end 150.
Database 120 can be DB2 database or SQL Server database, embodiment to the type of database 120 not
It limits, database 120 is for storing message, wherein message can be transmission message to be sent, be also possible to receive also
It is not issued to the subscription message at message subscribing end 150.Specifically, message desk 110 is based on sending the corresponding transmission of request generation
After message, by the transmission message storage into database 120, the benefit being arranged in this way be can to avoid message send failure when,
The situation for causing the data in system inconsistent because the message cannot be retransmitted, it should be noted that message desk 110 can
Corresponding transmission message to be stored to database 120, to avoid the loss of message according to the timing for sending request, wherein should
Storage can be persistent storage, i.e. transmission message can be permanently stored in database 120, and the storage for subscribing to message is also class
Seemingly, details are not described herein again.
Message-oriented middleware 130 is connect with message desk 110, can receive the transmission message of the transmission of message desk 110, can also
To send subscription message relevant to request is subscribed to message desk 110, the management and transmitting of message are completed.Specifically, message
Middleware 130 includes that Asynchronous message transfer and synchronization message transmit two ways, wherein synchronization message transmitting needs system synchronous
Processing business can not only reduce the experience of user when portfolio is larger, result even in system failure or paralysis, for this purpose, real
Example is applied using among message 120 Asynchronous message transfer mode, to reduce period of reservation of number, wherein message-oriented middleware 130 can
To be distributed message middleware.It should be noted that message desk 110 can be according to the corresponding timing of transmission message to set
Time interval is sent to message-oriented middleware 130, wherein sending the corresponding timing of message can be transmission corresponding with message is sent
The timing of request is also possible to message desk 110 and generates the timing for sending message, wherein message desk 110 is requested according to transmission
Timing generate corresponding transmission message.
Message sending end 140 can be the terminal for sending message, such as can be the intelligent terminals such as mobile phone or computer.
Message sending end 140 is either one or more, when message sending end 140 is multiple, can use same terminal,
Different terminals can also be used.Specifically, message sending end 140 can be used when message sending end 140 is using different terminals
ID come unique identification be sent to message desk 110 transmission request, avoid message from malfunctioning in the management process, for example, by end
The transmission request for holding M to send can be identified with M1, M2 and M3 respectively.Message subscribing end 150 is it can be appreciated that be message sink
Side is requested to message desk 110 for sending to subscribe to subscribe to message, when message desk 110 receives subscription request, parsing
The data structure of subscription request, specifies the message of its subscription, then receives 130 message sent among message, and this is disappeared
Breath is sent to message subscribing end 150.It is sent specifically, message desk 110 can receive message-oriented middleware 130 by message channel
Message, wherein message channel is pre-established according to business rule and type of message, and different message channel transmits different
The message of type, the benefit that message channel is arranged is: convenient for carrying out classification transmission to message, decreasing and receives specified message
Time.
The process of message transmission is briefly described below:
Message sending end 140, which is sent, specifically sends a request to message desk 110, and message desk 110 receives the transmission and asks
After asking, corresponding transmission message is generated according to request is sent, and message storage will be sent to data based on the timing for sending request
Library 120, and message-oriented middleware 130, such as the timing that can be generated according to message is sent are sent to according to certain transmission rule
It sends, when message-oriented middleware 130 receives the transmission message, which is stored at set time intervals,
When message subscribing end 150, which is sent, subscribes to request to message desk 110, data structure that message desk 110 requests the subscription
It is parsed, at this point, subscription message corresponding with parsing result is sent to message desk 110 by message-oriented middleware 130, by message
Platform 110 is sent to corresponding message subscribing end 150.
The embodiment of the present invention provides a kind of messaging system, comprising: message desk, database and message-oriented middleware, institute
Message desk is stated to connect with message subscribing end and message sending end respectively, the message desk also respectively with the database and institute
Message-oriented middleware connection is stated, the message sending end is sent to the message desk, the message desk for that will send request
Based on the transmission request generate send message, and according to it is described send request timing, by corresponding transmission message storage to
The database, and the transmission message is sent to the message-oriented middleware, the message subscribing end is asked for sending to subscribe to
It asks to the message desk, compared with traditional message-oriented middleware, the message desk of this programme is connect, both with message-oriented middleware
It can be used as the message producer, and can be used as message consumer, reduce the complexity of system, improve the performance of system,
Meanwhile by storing message to database, the integrality of message ensure that.
On the basis of the above embodiments, the transmission packet includes transaction message and non-transactional message, correspondingly,
When the transmission message is transaction message, message desk is used to disappear the transmission after message sending end confirmation
Breath is sent to message-oriented middleware；
When the transmission message is non-transactional message, message desk is used to the transmission message being transmitted directly to message
Middleware.
Specifically, transaction message be for guarantee the business of message sending end and message subscribing end in same affairs, i.e.,
Message sending end and message subscribing end have transactional relationship, if the business of message sending end executes failure, message subscribing end
Business also will fail, it is therefore desirable to message sending end send message authentication instruction, message sending end confirmation after, by message
Platform sends the message to message-oriented middleware.Whether non-transactional message has without the concern for message sending end and message subscribing end
Transactional relationship can directly be sent by message desk, the confirmation without message sending end.
Specifically, message desk generates corresponding transmission message according to request is sent if sending message is transaction message
Afterwards, by the transmission message duration to database, then replying ACK to message sending end, (Acknowledgement confirms word
Symbol), request is sent with notification message transmitting terminal and is sent successfully, message sending end executes local after receiving the confirmation message
Affairs, and confirmation instruction or rollback instruction are sent to message desk according to local matter implementing result, wherein confirmation instruction shows
Affairs success, rollback instruction show that affairs fail,.When message desk receives the confirmation instruction of message sending end transmission, by this
Transaction message is delivered to message-oriented middleware, and stores the message by message-oriented middleware, when message desk receives message sending end hair
When the rollback instruction sent, the transaction message is cancelled, without delivering.If transmission message is non-transactional message, message desk is being connect
After receiving the non-transactional message, directly by the message dilivery to message-oriented middleware.
On the basis of the above embodiments, message desk is also used to receive the subscription request that the message subscribing end is sent,
And subscription request is parsed.
Specifically, message subscribing end sent to message desk be subscribe to request, that is, subscribe to specific type message request,
After message desk receives subscription request, the data structure of subscription request is parsed, works out the message read to obtain
Information is sent to corresponding message subscribing end when message desk receives related news, such as when message subscribing end will subscribe to
Message be C1 message C1 is sent to message subscribing end when message desk receives message C1.
On the basis of the above embodiments, the message-oriented middleware, which is also used to send, subscribes to message to the message desk,
The message of subscribing to is the message corresponding with parsing result stored in the message-oriented middleware.
Specifically, the subscription message that message desk obtains subscribes to request when message desk parses from message-oriented middleware
Afterwards, it according to parsing result monitoring information channel, to receive the message of message-oriented middleware transmission, and transmits the message to message and orders
Read end, wherein different types of message is transmitted by different message channels, such as message subscribing end needs subscribing service class to disappear
Breath, and service class message is transmitted by message channel A, then message desk only needs monitoring information channel A, all without monitoring
Message channel improves and subscribes to accuracy and convenience that message obtains.
On the basis of the above embodiments, the message desk is also used to the subscription message being sent to the message and order
Read end.
It is understood that message subscribing end more than just one, when message subscribing end has multiple, message desk can root
Corresponding message subscribing end is sent respectively to by message is subscribed to according to the transmission rule of setting, wherein sending rule can be according to reality
Border needs to set, such as can be the priority according to message subscribing end, will subscribe to message prioritization and be sent to that priority is high to disappear
Subscription end is ceased, wherein the priority at message subscribing end can be stored in advance in information platform, subscribe to message when message desk obtains
Afterwards, corresponding priority is searched, the transmission of current subscription message is determined according to priority.It can also be according to message subscribing end
It is required that being sent, such as complete to send within setting time, message desk can preferentially be sent more urgent at this time
Message is subscribed to, the benefit being arranged in this way is can to guarantee to subscribe to the timeliness that message is sent with reasonable arrangement sending time.
On the basis of the above embodiments, the message desk is also used to disappear when the transmission for being sent to the message-oriented middleware
When ceasing or being sent to the subscription message transmission failure at the message subscribing end, strategy is retried according to preset message and retransmits institute
It states and sends message or the subscription message.
Specifically, due to network problem lead to message desk not and will send message normally issues or normal sending after by
It is caused to be not received by the transmission message extremely in message-oriented middleware itself, at this point, message desk can be according to preset message
It retrying strategy and retransmits the transmission message, wherein message retries strategy and can be to be sent with setting time interval, until
It sends successfully, when sending times reach frequency threshold value, will stop sending, wherein frequency threshold value can be set according to the actual situation
It sets, it can also be using the sending times of message desk default.Failure can be sent in addition to sending message, hair can also be had by subscribing to message
The case where sending unsuccessfully, such as when message subscribing end, which is broken down, causes not receiving subscription message, message desk equally understands root
Strategy is retried according to message and retransmits subscription message, and the retransmission process is similar with the retransmission process of message is sent, no longer superfluous herein
It states.
On the basis of the above embodiments, the message desk is also used to according to the number for sending message to the hair
Message is sent to carry out idempotent processing.
Specifically, the number of message can be the ID of message sending end corresponding with message is sent.Idempotence is using phase
Same parameter repeats same resource to call the result of some interface identical as primary result is called, mathematical expression form are as follows: f
(f (x))=f (x).Message idempotence is that same message is consistent by the effect that application is repeatedly once generated with application, in this way
The benefit of processing is: can guarantee that message is successfully transmitted once, it is assumed that without the processing, when due to network cause, message is flat
When whether the uncertain message-oriented middleware of platform receives transmission message, retransmit once, then message-oriented middleware can receive identical twice
Transmission message cause on the basis of adding 1 again plus 1 due to repeating to send, result is obvious if the transmission message is plus 1
It does not conform to the actual conditions, seriously reduces the reliability of system.Wherein, message desk is to the specific mistake for sending message progress idempotent processing
Journey embodiment is not construed as limiting, for example, can according to the ID of message sending end to every transmission message generate a unique mark come
The foundation for marking the transmission message to handle as idempotent.
On the basis of the above embodiments, the message desk is also used to be ordered according to the number for subscribing to message to described
It reads message and carries out idempotent processing.
The number for subscribing to message can be the ID for sending the message subscribing end for subscribing to request, carry out at idempotent to message is subscribed to
The process of reason is similar with the message progress process of idempotent processing is sent, and details are not described herein again.
Complete message process once is described below by the signal flow graph of a message transmission:
With reference to Fig. 2-Fig. 3, wherein Fig. 2 is the time diagram that transaction message executes, Fig. 3 be non-transactional message execute when
Sequence schematic diagram.With reference to Fig. 2, message sending end sends transaction message to message desk, message desk receive the transaction message with
Afterwards, it is persisted to database, it is abnormal to avoid occurring in message transmitting process, lead to the problem that data are inconsistent, simultaneously
Message can be sent to corresponding message sending end and send successful information, with notification message transmitting terminal transaction message send at
Function, message sending end executes local matter after receiving the information, and sends to message desk and confirm that instruction or rollback refer to
Enable, if message desk receive be confirmation instruction, show that affairs run succeeded, which can be delivered to message
Middleware shows that affairs execute failure if what is received is rollback instruction, needs the transaction message that receives of revocation, not into
Row is delivered.When message subscribing end needs to subscribe to message, sends and subscribe to request to message desk, message desk requests the subscription
It is parsed, and is sent according to parsing result to message-oriented middleware and subscribe to messaging service, at the same time, message desk monitoring information
Channel, the message relevant to request is subscribed to sent with monitoring information middleware, when message desk receives message-oriented middleware hair
After the message sent, parse simultaneously update message state to the message, be ultimately sent to message subscribing end.
With reference to Fig. 3, when the message that message sending end is sent is non-transactional message, confirmation is sent without message sending end and is referred to
It enables or rollback instruction, message desk is directly delivered to message-oriented middleware when receiving the non-transactional message.When message is flat
When platform receives subscription request, request is subscribed in parsing, and is sent according to parsing result to message-oriented middleware and subscribed to messaging service, and
The message relevant to request is subscribed to that monitoring information channel is sent with monitoring information middleware, when message desk receives in message
Between after the message that sends of part, which parse and update message state, is ultimately sent to message subscribing end.
Note that the above is only a better embodiment of the present invention and the applied technical principle.It will be appreciated by those skilled in the art that
The invention is not limited to the specific embodiments described herein, be able to carry out for a person skilled in the art it is various it is apparent variation,
It readjusts and substitutes without departing from protection scope of the present invention.Therefore, although being carried out by above embodiments to the present invention
It is described in further detail, but the present invention is not limited to the above embodiments only, without departing from the inventive concept, also
It may include more other equivalent embodiments, and the scope of the invention is determined by the scope of the appended claims.
Claims (8)
1. a kind of messaging system characterized by comprising message desk, database and message-oriented middleware；
The message desk is connect with message subscribing end and message sending end respectively, the message desk also respectively with the data
Library is connected with the message-oriented middleware,
The message sending end is sent to the message desk for that will send request, and the message desk, which is based on the transmission, asks
It seeks survival into and sends message, and according to the timing for sending request, by the storage of corresponding transmission message to the database, and will
The transmission message is sent to the message-oriented middleware, and the message subscribing end requests to put down to the message for sending to subscribe to
Platform.
2. system according to claim 1, which is characterized in that the transmission packet includes transaction message and non-transactional disappears
Breath, correspondingly,
When the transmission message is transaction message, the message desk is used to disappear the transmission after message sending end confirmation
Breath is sent to the message-oriented middleware；
When the transmission message is non-transactional message, the message desk is used to for the transmission message being transmitted directly to described
Message-oriented middleware.
3. system according to claim 1, which is characterized in that the message desk is also used to receive the message subscribing end
The subscription of transmission is requested, and is parsed to subscription request.
4. system according to claim 3, which is characterized in that the message-oriented middleware, which is also used to send, subscribes to message to institute
Message desk is stated, the message of subscribing to is the message corresponding with parsing result stored in the message-oriented middleware.
5. system according to claim 4, which is characterized in that the message desk is also used to send the subscription message
To the message subscribing end.
6. system according to claim 5, which is characterized in that the message desk is also used to work as and be sent in the message
Between part transmission message or be sent to the message subscribing end subscription message send failure when, plan is retried according to preset message
Slightly retransmit the transmission message or the subscription message.
7. system according to claim 1, which is characterized in that the message desk is also used to according to the transmission message
Number carries out idempotent processing to the transmission message.
8. system according to claim 1, which is characterized in that the message desk is also used to according to the subscription message
Number carries out idempotent processing to the subscription message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811386086.0A CN109451032B (en) | 2018-11-20 | 2018-11-20 | Message transmission system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811386086.0A CN109451032B (en) | 2018-11-20 | 2018-11-20 | Message transmission system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109451032A true CN109451032A (en) | 2019-03-08 |
| CN109451032B CN109451032B (en) | 2021-11-23 |
Family
ID=65553388
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811386086.0A Active CN109451032B (en) | 2018-11-20 | 2018-11-20 | Message transmission system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109451032B (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109922151A (en) * | 2019-03-12 | 2019-06-21 | 浪潮通用软件有限公司 | A kind of data sharing method between micro services |
| CN110392120A (en) * | 2019-08-15 | 2019-10-29 | 锐捷网络股份有限公司 | The restoration methods and device of failure during a kind of push of message |
| CN110941502A (en) * | 2019-12-16 | 2020-03-31 | 广州市百果园信息技术有限公司 | Message processing method, device, storage medium and equipment |
| CN110995851A (en) * | 2019-12-11 | 2020-04-10 | 贝壳技术有限公司 | Message processing method, device, storage medium and equipment |
| CN111818112A (en) * | 2019-04-11 | 2020-10-23 | 中国移动通信集团四川有限公司 | Kafka system-based message sending method and device |
| CN112202781A (en) * | 2020-09-30 | 2021-01-08 | 广东巴金斯科技有限公司 | E-commerce large data volume receipt message processing method, device and system |
| CN112783910A (en) * | 2021-01-29 | 2021-05-11 | 浪潮通用软件有限公司 | Data distribution method and system based on message middleware |
| CN114244899A (en) * | 2021-12-02 | 2022-03-25 | 上海微盟企业发展有限公司 | Message transmission method and device and readable storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090070480A1 (en) * | 2002-12-04 | 2009-03-12 | Silicon Graphis, Inc. | System and Method for Conveying Information |
| US20100333111A1 (en) * | 2009-06-29 | 2010-12-30 | Software Ag | Systems and/or methods for policy-based JMS broker clustering |
| CN102255934A (en) * | 2010-05-20 | 2011-11-23 | 中兴通讯股份有限公司 | Cloud service publishing method, cloud service publishing interface message packet and cloud service broker |
| CN104092767A (en) * | 2014-07-21 | 2014-10-08 | 北京邮电大学 | Posting/subscribing system for adding message queue models and working method thereof |
| CN105068864A (en) * | 2015-07-24 | 2015-11-18 | 北京京东尚科信息技术有限公司 | Method and system for processing asynchronous message queue |
| CN105871959A (en) * | 2015-01-22 | 2016-08-17 | 阿里巴巴集团控股有限公司 | Message delivery method, system and device |
| WO2018151797A1 (en) * | 2017-02-17 | 2018-08-23 | Home Box Office, Inc. | Endpoint abstraction for service-to-service communication |
-
2018
- 2018-11-20 CN CN201811386086.0A patent/CN109451032B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090070480A1 (en) * | 2002-12-04 | 2009-03-12 | Silicon Graphis, Inc. | System and Method for Conveying Information |
| US20100333111A1 (en) * | 2009-06-29 | 2010-12-30 | Software Ag | Systems and/or methods for policy-based JMS broker clustering |
| CN102255934A (en) * | 2010-05-20 | 2011-11-23 | 中兴通讯股份有限公司 | Cloud service publishing method, cloud service publishing interface message packet and cloud service broker |
| CN104092767A (en) * | 2014-07-21 | 2014-10-08 | 北京邮电大学 | Posting/subscribing system for adding message queue models and working method thereof |
| CN105871959A (en) * | 2015-01-22 | 2016-08-17 | 阿里巴巴集团控股有限公司 | Message delivery method, system and device |
| CN105068864A (en) * | 2015-07-24 | 2015-11-18 | 北京京东尚科信息技术有限公司 | Method and system for processing asynchronous message queue |
| WO2018151797A1 (en) * | 2017-02-17 | 2018-08-23 | Home Box Office, Inc. | Endpoint abstraction for service-to-service communication |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109922151A (en) * | 2019-03-12 | 2019-06-21 | 浪潮通用软件有限公司 | A kind of data sharing method between micro services |
| CN111818112A (en) * | 2019-04-11 | 2020-10-23 | 中国移动通信集团四川有限公司 | Kafka system-based message sending method and device |
| CN110392120A (en) * | 2019-08-15 | 2019-10-29 | 锐捷网络股份有限公司 | The restoration methods and device of failure during a kind of push of message |
| CN110392120B (en) * | 2019-08-15 | 2022-06-21 | 锐捷网络股份有限公司 | Method and device for recovering fault in message pushing process |
| CN110995851A (en) * | 2019-12-11 | 2020-04-10 | 贝壳技术有限公司 | Message processing method, device, storage medium and equipment |
| CN110995851B (en) * | 2019-12-11 | 2021-12-24 | 贝壳找房(北京)科技有限公司 | Message processing method, device, storage medium and equipment |
| CN110941502A (en) * | 2019-12-16 | 2020-03-31 | 广州市百果园信息技术有限公司 | Message processing method, device, storage medium and equipment |
| CN112202781A (en) * | 2020-09-30 | 2021-01-08 | 广东巴金斯科技有限公司 | E-commerce large data volume receipt message processing method, device and system |
| CN112783910A (en) * | 2021-01-29 | 2021-05-11 | 浪潮通用软件有限公司 | Data distribution method and system based on message middleware |
| CN114244899A (en) * | 2021-12-02 | 2022-03-25 | 上海微盟企业发展有限公司 | Message transmission method and device and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109451032B (en) | 2021-11-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109451032A (en) | A kind of messaging system | |
| CN107087033B (en) | Message pushing method and device, storage medium and computer equipment | |
| CN110601952A (en) | Multi-channel message notification sending method and device | |
| CN110808948B (en) | Remote procedure calling method, device and system | |
| CN111277639B (en) | Method and device for maintaining data consistency | |
| CN104811459A (en) | Processing method, processing device and system for message services and message service system | |
| US20120203850A1 (en) | Folder transmission method and system | |
| CN102143194A (en) | Data synchronization method and system, immediate data node and terminal data node | |
| CN112187629B (en) | Message revocation method for 5G communication, computer device and computer-readable storage medium | |
| CN110413425B (en) | Third-party message callback method, device, server and storage medium | |
| CN103177368A (en) | Reconciliation method and system for electronic commerce system | |
| CN111784329B (en) | Service data processing method and device, storage medium and electronic device | |
| CN112910679B (en) | Multi-level remote upgrading method for power Internet of things | |
| CN103731465A (en) | Distributed system and transaction treatment method thereof | |
| CN105871819B (en) | Transfer control method and equipment | |
| CN110233883A (en) | Processing method, device, server and the storage medium of PUSH message | |
| CN114448719B (en) | Message interaction method, device and system | |
| CN102984174A (en) | Method and system for reliability guarantee in publish-subscribe system | |
| CN102801782B (en) | A kind of synchronous updating method of data and system | |
| CN112583743B (en) | Distributed file exchange method and device | |
| WO2019042032A1 (en) | Data transmission method, rlc entity and pdcp entity | |
| WO2023186154A1 (en) | Data transmission system and method | |
| CN112328560A (en) | File scheduling method and system | |
| CN102684865B (en) | Method, system and device for data synchronization | |
| CN104993970A (en) | Centralized monitoring method of distributed system key operation index 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |