CN111049915A - Message queue agent grid under container cloud and method - Google Patents
Message queue agent grid under container cloud and method Download PDFInfo
- Publication number
- CN111049915A CN111049915A CN201911307556.4A CN201911307556A CN111049915A CN 111049915 A CN111049915 A CN 111049915A CN 201911307556 A CN201911307556 A CN 201911307556A CN 111049915 A CN111049915 A CN 111049915A
- Authority
- CN
- China
- Prior art keywords
- message queue
- message
- agent
- broker
- proxy
- 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
Images
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/566—Grouping or aggregating service requests, e.g. for unified processing
-
- 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/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- 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/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a container under-cloud message queue agent grid, which comprises: a virtual machine, a plurality of container engines, and a message queue agent; wherein: the plurality of container engines and the message queue agents are respectively deployed on the virtual machines; the container engine is used for deploying a message producer or a message consumer of the message queue; a container engine of a message producer or a message consumer for deploying a message queue is connected with the message queue agent; the message queue broker is connected to the message queue broker and the registry. The invention can effectively solve the problem of multi-language and service management of the message queue sender and the consumer, and can solve the problem that some consumers are idle because of too many consumers and cannot take the message. The invention also discloses a container under-cloud message queue agent method.
Description
Technical Field
The application relates to the technical field of micro services, in particular to a container under-cloud message queue agent grid and a method.
Background
With the rapid development and wide popularization of the container cloud, the architecture technology of the micro-service has changed greatly. The former service instances are all in units of virtual machines, but now are all in units of containers, and the number of instances is greatly increased. Moreover, the internal communication on the same machine does not occupy the network bandwidth, the performance is very high, and the structural change prompts the generation of a new micro-service architecture, namely a service grid, but the service grid only solves the intercommunication of micro-services directly and has no solution on a message queue.
Disclosure of Invention
In view of this, the application provides a container under-cloud message queue agent grid, which can effectively solve the problem of multi-language and service management of message queue senders and consumers, and can solve the problem that some consumers are idle because of too many consumers and cannot take messages.
The application provides a container under-cloud message queue agent grid, including: a virtual machine, a plurality of container engines, and a message queue agent; wherein:
the plurality of container engines and the message queue agent are respectively deployed on the virtual machine;
the container engine is used for deploying a message producer or a consumer of a message queue;
the container engine of a message producer or consumer deploying a message queue is connected with the message queue agent;
the message queue broker is connected to a broker and a registry of message queues.
Preferably, the message queue agent is connected with the message queue broker and the registry via a transmission control protocol.
Preferably, the message producer of the message queue is connected to the message queue agent by means of hypertext transfer protocol.
Preferably, the message producer of the message queue is connected to the message queue proxy through a remote procedure call.
Preferably, the registry comprises: a name server.
A container under-cloud message queue agent method comprises the following steps:
a message producer of the message queue sends a message to a message queue agent;
and the message queue agent sends the received message to a broker and a registration center of a message queue.
Preferably, the sending of the message to the message queue agent by the message producer of the message queue comprises:
the message producer of the message queue sends the message to the message queue agent via hypertext transfer protocol.
Preferably, the message queue broker sending the received message to a message queue broker and a registry comprises:
and the message queue agent sends the received message to a broker and a registration center of a message queue through a transmission control protocol.
Preferably, the method further comprises:
when a consumer of the message queue consumes a message, requesting the message queue agent for the message;
the message queue agent requesting messages from brokers of the message queue;
and returning the response piece after successful consumption to the broker of the message queue.
Preferably, the message queue agent requesting messages from the broker of the message queue comprises:
the message queue agent requests messages from brokers of the message queue via a transmission control protocol.
In summary, the present invention discloses a container under-cloud message queue proxy grid, which includes: a virtual machine, a plurality of container engines, and a message queue agent; wherein: the container engines and the message queue agents are respectively deployed on the virtual machines; the container engine is used for deploying a message producer or a message consumer of the message queue; a container engine of a message producer or a message consumer for deploying a message queue is connected with the message queue agent; the message queue broker is connected to the message queue broker and the registry. The invention can effectively solve the problem of multi-language and service management of the message queue sender and the consumer, and can solve the problem that some consumers are idle because of too many consumers and cannot take the message.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic structural diagram of an embodiment 1 of a container cloud message queue proxy grid disclosed in the present invention;
fig. 2 is a schematic structural diagram of an embodiment 1 of a container under-cloud message queue proxy grid disclosed in the present invention;
fig. 3 is a flowchart of an embodiment 1 of a container under-cloud message queue agent method disclosed in the present invention;
fig. 4 is a flowchart of an embodiment 2 of a container under-cloud message queue agent method disclosed in the present invention;
fig. 5 is a flowchart of an embodiment 3 of a container under-cloud message queue agent method disclosed in the present invention;
fig. 6 is a flowchart of an embodiment 4 of a container under-cloud message queue agent method disclosed in the present invention;
fig. 7 is a flowchart of a method for container cloud message queue proxy according to embodiment 5 of the present disclosure.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
As shown in fig. 1, the message queue agent grid under container cloud disclosed by the present invention includes: the virtual machine VM, a plurality of container engines dockers and a message queue agent MQ Proxy; wherein:
a plurality of container engines docker and message queue agent MQ Proxy are respectively deployed on the virtual machine VM;
the container engine docker is used for deploying a message producer or a consumer of the message queue;
it should be noted that the message Producer of the message queue may be C + + Producer, Node JS Producer, and Python Producer. The consumer consumers may be C + + consumers, Node JS P consumers, and Python consumers.
As shown in fig. 2, the container engine docker of the message producer C + + producer, Node JS P producer and Python producer or the consumer C + + consumer, Node JS P consumer and Python consumer of the deployment message queue is connected to the message queue agent MQ Proxy;
the message queue agent MQ Proxy is connected to the Broker and the registry of message queues.
Note that Broker for message queue can be Kafka Broker and socket MQBroker. The registry may be a zookeeper or Name Server.
Specifically, the message queue agent MQ Proxy, Kafka Broker and socket MQBroker of the message queue, and the registry zookeeper or Name Server may be connected through a transmission control protocol.
In the above embodiment, one virtual machine has multiple docker instances, and the dockers may have producers or consumers of MQs deployed thereon.
The MQ Proxy is not deployed in a docker mode, but is directly deployed on the virtual machine in a system service mode.
Because the MQ Proxy is deployed in a mode that the system service is directly deployed on the virtual machine, the Producer and the MQProxy are in local communication, and the performance is good.
And the MQ Proxy integrates service management capabilities such as fusing, retrying, monitoring, load balancing and the like.
The Producer and Consumer are not directly connected to the brooker of MQ, but are connected to MQ proxy.
MQ Proxy connects with MQ Broker and registry such as zookeeper or Name Server.
When the Producer sends the message, the message is sent to MQ Proxy, which is Http or Thrift RPC, so that multi-language support is provided.
After the MQ Proxy receives the message, the message may be forwarded to Kafka Broker or Rocket MQ Broker, where multi-MQ support is provided.
When the Consumer consumes the message, the message is requested from the MQ Proxy, and then the message is requested from the Broker by the MQ Proxy. The receipt after successful consumption is also returned to the Broker in turn. A mode of HTTP long polling consumption message is also provided, and multi-language is supported.
In summary, in the above embodiments, after the consumer migrates from the virtual machine to the docker, the docker allocates fewer resources (CPU, memory, etc.), so the number of instances is much larger than the number of virtual machines. On a mainstream message queue, such changes can result in some consumers not consuming data.
After introducing the MQ Proxy, the MQ Proxy consumes the partition data and can be consistent with the number of partitions at most. The consumers interact with the MQ Proxy, and one MQ Proxy can provide a Proxy for a plurality of consumers, so that the scalability is greatly improved, and the method is particularly suitable for slow consumption scenes. Thereby greatly improving the throughput of the scalable type and the system.
As shown in fig. 3, which is a flowchart of a method in embodiment 1 of a method for container-under-cloud message queue proxy disclosed in the present invention, the method may include the following steps:
s301, a message producer of the message queue sends a message to a message queue agent;
based on the container under-cloud message queue agent grid disclosed by the embodiment, when a message Producer of a message queue sends a message, the message is sent to a message queue agent MQ Proxy.
S302, the message queue agent sends the received message to a broker and a registration center of the message queue.
After the message queue agent MQ Proxy receives the message, the message queue agent MQ Proxy can forward the received message to a Broker Kafka Broker or a socket MQ Broker of the message queue and a registry zookeeper or a Name Server.
As shown in fig. 4, which is a flowchart of a method in embodiment 2 of a container under-cloud message queue agent method disclosed in the present invention, the method may include the following steps:
s401, a message producer of a message queue sends a message to a message queue agent through a hypertext transfer protocol;
based on the container under-cloud message queue agent grid disclosed by the embodiment, when a message Producer of a message queue sends a message, the message is sent to a message queue agent MQ Proxy.
Specifically, when the message Producer of the message queue sends a message, the message Producer can send the message to the message queue agent MQ Proxy through the hypertext transfer protocol.
S402, the message queue agent sends the received message to the message queue broker and the registration center.
After the message queue agent MQ Proxy receives the message, the message queue agent MQ Proxy can forward the received message to a Broker Kafka Broker or a socket MQ Broker of the message queue and a registry zookeeper or a Name Server.
As shown in fig. 5, which is a flowchart of a method in embodiment 3 of a method for container-under-cloud message queue brokering, the method may include the following steps:
s501, a message producer of the message queue sends a message to a message queue agent through a hypertext transfer protocol;
based on the container under-cloud message queue agent grid disclosed by the embodiment, when a message Producer of a message queue sends a message, the message is sent to a message queue agent MQ Proxy.
Specifically, when the message Producer of the message queue sends a message, the message Producer can send the message to the message queue agent MQ Proxy through the hypertext transfer protocol.
S502, the message queue agent sends the received message to the message queue broker and the registration center through the transmission control protocol.
After the message queue agent MQ Proxy receives the message, the message queue agent MQ Proxy can forward the received message to a Broker Kafka Broker or a socket MQ Broker of the message queue and a registry zookeeper or a Name Server.
Specifically, after the message queue agent MQ Proxy receives the message, the received message can be forwarded to the Broker Kafka Broker or socket MQ Broker and the registry zookeeper or Name Server of the message queue through the transmission control protocol.
As shown in fig. 6, which is a flowchart of a method in embodiment 4 of a method for container-under-cloud message queue brokering, the method may include the following steps:
s601, a message producer of the message queue sends a message to a message queue agent through a hypertext transfer protocol;
based on the container under-cloud message queue agent grid disclosed by the embodiment, when a message Producer of a message queue sends a message, the message is sent to a message queue agent MQ Proxy.
Specifically, when the message Producer of the message queue sends a message, the message Producer can send the message to the message queue agent MQ Proxy through the hypertext transfer protocol.
S602, the message queue agent sends the received message to a broker and a registration center of the message queue through a transmission control protocol;
after the message queue agent MQ Proxy receives the message, the message queue agent MQ Proxy can forward the received message to a Broker Kafka Broker or a socket MQ Broker of the message queue and a registry zookeeper or a Name Server.
Specifically, after the message queue agent MQ Proxy receives the message, the received message can be forwarded to the Broker Kafka Broker or socket MQ Broker and the registry zookeeper or Name Server of the message queue through the transmission control protocol.
S603, when the consumers of the message queue consume the messages, requesting the messages from the message queue agent;
when a Consumer Consumer of a message queue consumes a message, the Consumer firstly requests the message from the MQ Proxy.
S604, the message queue agent requests the message from the broker of the message queue;
the message queue Proxy MQ Proxy in turn requests messages from the Broker of the message queue.
And S605, returning the response piece after successful consumption to the broker of the message queue.
The response pieces after successful consumption are also sequentially returned to the Broker of the message queue.
As shown in fig. 7, which is a flowchart of a method in embodiment 5 of a method for container-under-cloud message queue brokering, the method may include the following steps:
s701, a message producer of the message queue sends a message to a message queue agent through a hypertext transfer protocol;
based on the container under-cloud message queue agent grid disclosed by the embodiment, when a message Producer of a message queue sends a message, the message is sent to a message queue agent MQ Proxy.
Specifically, when the message Producer of the message queue sends a message, the message Producer can send the message to the message queue agent MQ Proxy through the hypertext transfer protocol.
S702, the message queue agent sends the received message to a broker and a registration center of the message queue through a transmission control protocol;
after the message queue agent MQ Proxy receives the message, the message queue agent MQ Proxy can forward the received message to a Broker Kafka Broker or a socket MQ Broker of the message queue and a registry zookeeper or a Name Server.
Specifically, after the message queue agent MQ Proxy receives the message, the received message can be forwarded to the Broker Kafka Broker or socket MQ Broker and the registry zookeeper or Name Server of the message queue through the transmission control protocol.
S703, when the consumer in the message queue consumes the message, requesting the message queue agent for the message;
when a Consumer Consumer of a message queue consumes a message, the Consumer firstly requests the message from the MQ Proxy.
S704, the message queue agent requests messages from the broker of the message queue through a transmission control protocol;
the message queue Proxy MQ Proxy in turn requests messages from the Broker of the message queue. In particular, the message queue agent MQ Proxy may request messages from the Broker of the message queue via a transport control protocol.
And S705, returning the response piece after successful consumption to the broker of the message queue.
The response pieces after successful consumption are also sequentially returned to the Broker of the message queue.
In conclusion, the invention supports multiple languages, and the messages can be sent without introducing a client of MQ in various languages. And multiple MQs are seamlessly supported, and a user does not need to change codes. The performance loss is small, because the sender, the consumer and the agent are all in local communication, the performance loss is small. The expansibility is strong, the consumers of the original MQ can not exceed the fragment number, and when the fragment number is exceeded, the consumers can not consume the messages. According to the scheme, one agent can manage a plurality of consumers, so that the expansibility is improved by many times.
The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A container undersubble message queue proxy grid, comprising: a virtual machine, a plurality of container engines, and a message queue agent; wherein:
the plurality of container engines and the message queue agent are respectively deployed on the virtual machine;
the container engine is used for deploying a message producer or a consumer of a message queue;
the container engine of a message producer or consumer deploying a message queue is connected with the message queue agent;
the message queue broker is connected to a broker and a registry of message queues.
2. The proxy grid of claim 1, wherein said message queue proxy is connected to message queue brokers and registries via a transmission control protocol.
3. The proxy grid according to claim 1, wherein the message producer of said message queue is connected to said message queue proxy via hypertext transfer protocol.
4. The proxy grid according to claim 1, wherein the message producer of said message queue is connected to said message queue proxy through a remote procedure call.
5. The proxy grid according to claim 1, wherein said registry comprises: a name server.
6. A container under-cloud message queue agent method is characterized by comprising the following steps:
a message producer of the message queue sends a message to a message queue agent;
and the message queue agent sends the received message to a broker and a registration center of a message queue.
7. The method of claim 6, wherein sending a message to a message queue agent by a message producer of the message queue comprises:
the message producer of the message queue sends the message to the message queue agent via hypertext transfer protocol.
8. The method of claim 6, wherein the message queue agent sending the received message to a message queue broker and a registry comprises:
and the message queue agent sends the received message to a broker and a registration center of a message queue through a transmission control protocol.
9. The method of claim 6, further comprising:
when a consumer of the message queue consumes a message, requesting the message queue agent for the message;
the message queue agent requesting messages from brokers of the message queue;
and returning the response piece after successful consumption to the broker of the message queue.
10. The method of claim 9, wherein requesting messages from a broker of the message queue by the message queue agent comprises:
the message queue agent requests messages from brokers of the message queue via a transmission control protocol.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911307556.4A CN111049915B (en) | 2019-12-17 | 2019-12-17 | Container under-cloud message queue agent system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911307556.4A CN111049915B (en) | 2019-12-17 | 2019-12-17 | Container under-cloud message queue agent system and method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111049915A true CN111049915A (en) | 2020-04-21 |
| CN111049915B CN111049915B (en) | 2023-04-07 |
Family
ID=70237529
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911307556.4A Active CN111049915B (en) | 2019-12-17 | 2019-12-17 | Container under-cloud message queue agent system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111049915B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113703997A (en) * | 2021-08-16 | 2021-11-26 | 北京图菱视频科技有限公司 | Bidirectional asynchronous communication middleware system integrating multiple message agents and implementation method |
| CN114924768A (en) * | 2022-05-16 | 2022-08-19 | 阿里巴巴（中国）有限公司 | Application program updating method, device and system and electronic equipment |
| CN115334155A (en) * | 2022-08-12 | 2022-11-11 | 中国建设银行股份有限公司 | Message queue agent method and device |
Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6067477A (en) * | 1998-01-15 | 2000-05-23 | Eutech Cybernetics Pte Ltd. | Method and apparatus for the creation of personalized supervisory and control data acquisition systems for the management and integration of real-time enterprise-wide applications and systems |
| CN1516419A (en) * | 2002-12-23 | 2004-07-28 | 国际商业机器公司 | Syste mand method for processing customer computer request on host computer network |
| US20050044197A1 (en) * | 2003-08-18 | 2005-02-24 | Sun Microsystems.Inc. | Structured methodology and design patterns for web services |
| CN102255935A (en) * | 2010-05-20 | 2011-11-23 | 中兴通讯股份有限公司 | Cloud service consumption method, cloud service message packet, cloud service broker and cloud system |
| US8271996B1 (en) * | 2008-09-29 | 2012-09-18 | Emc Corporation | Event queues |
| CN103856393A (en) * | 2013-07-09 | 2014-06-11 | 携程计算机技术（上海）有限公司 | Distributed message-oriented middleware system based on database and operating method thereof |
| US20150006729A1 (en) * | 2013-06-26 | 2015-01-01 | Amazon Technologies, Inc. | Producer system partitioning among leasing agent systems |
| US20160132214A1 (en) * | 2014-11-11 | 2016-05-12 | Amazon Technologies, Inc. | Application delivery agents on virtual desktop instances |
| CN105791402A (en) * | 2016-03-02 | 2016-07-20 | 付宏伟 | Network virtualization realization method of cloud computing platform and corresponding plug-in and agent |
| CN106385435A (en) * | 2016-08-30 | 2017-02-08 | 乐视控股（北京）有限公司 | Service treatment method and system of service system |
| US20170078216A1 (en) * | 2013-10-17 | 2017-03-16 | Ciena Corporation | Method and apparatus for provisioning virtual network functions from a network service provider |
| CN107566493A (en) * | 2017-09-06 | 2018-01-09 | 中国科学院信息工程研究所 | A kind of agent node creation method, service means for acting as agent and system towards complicated user's request |
| CN108306941A (en) * | 2018-01-05 | 2018-07-20 | 上海你我贷互联网金融信息服务有限公司 | A kind of distributed information system |
| US10091297B1 (en) * | 2016-05-18 | 2018-10-02 | EMC IP Holding Company LLC | Data processing and data movement in cloud computing environment |
| CN109656725A (en) * | 2018-11-09 | 2019-04-19 | 北京字节跳动网络技术有限公司 | Message consumer's switching method, device, storage medium and electronic equipment |
| CN109951320A (en) * | 2019-02-25 | 2019-06-28 | 武汉大学 | A kind of expansible multi layer monitoing frame and its monitoring method of facing cloud platform |
| CN110113420A (en) * | 2019-05-08 | 2019-08-09 | 重庆大学 | Distributed Message Queue management system based on NVM |
-
2019
- 2019-12-17 CN CN201911307556.4A patent/CN111049915B/en active Active
Patent Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6067477A (en) * | 1998-01-15 | 2000-05-23 | Eutech Cybernetics Pte Ltd. | Method and apparatus for the creation of personalized supervisory and control data acquisition systems for the management and integration of real-time enterprise-wide applications and systems |
| CN1516419A (en) * | 2002-12-23 | 2004-07-28 | 国际商业机器公司 | Syste mand method for processing customer computer request on host computer network |
| US20050044197A1 (en) * | 2003-08-18 | 2005-02-24 | Sun Microsystems.Inc. | Structured methodology and design patterns for web services |
| US8271996B1 (en) * | 2008-09-29 | 2012-09-18 | Emc Corporation | Event queues |
| CN102255935A (en) * | 2010-05-20 | 2011-11-23 | 中兴通讯股份有限公司 | Cloud service consumption method, cloud service message packet, cloud service broker and cloud system |
| US20150006729A1 (en) * | 2013-06-26 | 2015-01-01 | Amazon Technologies, Inc. | Producer system partitioning among leasing agent systems |
| CN103856393A (en) * | 2013-07-09 | 2014-06-11 | 携程计算机技术（上海）有限公司 | Distributed message-oriented middleware system based on database and operating method thereof |
| US20170078216A1 (en) * | 2013-10-17 | 2017-03-16 | Ciena Corporation | Method and apparatus for provisioning virtual network functions from a network service provider |
| US20160132214A1 (en) * | 2014-11-11 | 2016-05-12 | Amazon Technologies, Inc. | Application delivery agents on virtual desktop instances |
| CN105791402A (en) * | 2016-03-02 | 2016-07-20 | 付宏伟 | Network virtualization realization method of cloud computing platform and corresponding plug-in and agent |
| US10091297B1 (en) * | 2016-05-18 | 2018-10-02 | EMC IP Holding Company LLC | Data processing and data movement in cloud computing environment |
| CN106385435A (en) * | 2016-08-30 | 2017-02-08 | 乐视控股（北京）有限公司 | Service treatment method and system of service system |
| CN107566493A (en) * | 2017-09-06 | 2018-01-09 | 中国科学院信息工程研究所 | A kind of agent node creation method, service means for acting as agent and system towards complicated user's request |
| CN108306941A (en) * | 2018-01-05 | 2018-07-20 | 上海你我贷互联网金融信息服务有限公司 | A kind of distributed information system |
| CN109656725A (en) * | 2018-11-09 | 2019-04-19 | 北京字节跳动网络技术有限公司 | Message consumer's switching method, device, storage medium and electronic equipment |
| CN109951320A (en) * | 2019-02-25 | 2019-06-28 | 武汉大学 | A kind of expansible multi layer monitoing frame and its monitoring method of facing cloud platform |
| CN110113420A (en) * | 2019-05-08 | 2019-08-09 | 重庆大学 | Distributed Message Queue management system based on NVM |
Non-Patent Citations (6)
| Title |
|---|
| NAM-LUC TRAN: ""EQS: An Elastic and Scalable Message Queue for the Cloud"", 《2011 IEEE THIRD INTERNATIONAL CONFERENCE ON CLOUD COMPUTING TECHNOLOGY AND SCIENCE》 * |
| 仇臣: ""Docker容器的性能监控和日志服务的设计与实现"", 《万方》 * |
| 叶长风: ""spring cloud 与 docker-compose构建微服务"", 《HTTPS://BLOG.CSDN.NET/U012734441/ARTICLE/DETAILS/77832797》 * |
| 李锐等: "《EP Cloud实训教程》", 31 January 2019, 华南理工大学出版社 * |
| 物联网电子世界: ""rabbitMQ消息队列入门介绍"", 《HTTPS://BAIJIAHAO.BAIDU.COM/S?ID=1623017666101002265&WFR=SPIDER&FOR=PC》 * |
| 癫狂侠: ""消息中间件—RabbitMQ"", 《HTTPS://WWW.JIANSHU.COM/P/6376936845FF》 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113703997A (en) * | 2021-08-16 | 2021-11-26 | 北京图菱视频科技有限公司 | Bidirectional asynchronous communication middleware system integrating multiple message agents and implementation method |
| CN114924768A (en) * | 2022-05-16 | 2022-08-19 | 阿里巴巴（中国）有限公司 | Application program updating method, device and system and electronic equipment |
| CN115334155A (en) * | 2022-08-12 | 2022-11-11 | 中国建设银行股份有限公司 | Message queue agent method and device |
| CN115334155B (en) * | 2022-08-12 | 2024-04-19 | 中国建设银行股份有限公司 | Message queue proxy method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111049915B (en) | 2023-04-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111049915B (en) | Container under-cloud message queue agent system and method | |
| US20040024861A1 (en) | Network load balancing | |
| EP1760989A1 (en) | Web Services in a peer to peer network | |
| CN102281190A (en) | Networking method for load balancing apparatus, server and client access method | |
| Erradi et al. | A broker-based approach for improving Web services reliability | |
| WO2010027609A2 (en) | Load balancing for services | |
| US7051118B2 (en) | Method and apparatus for anonymous subject-based addressing | |
| CN113965628B (en) | Message scheduling method, server and storage medium | |
| CN111131470B (en) | Terminal device, data processing method thereof and data processing system | |
| US20090132582A1 (en) | Processor-server hybrid system for processing data | |
| US12120205B2 (en) | Communication protocol for a distributed event streaming platform | |
| Skjervold et al. | Enabling publish/subscribe with cots web services across heterogeneous networks | |
| CN114051030B (en) | Communication method, communication device, intelligent community system and storage medium | |
| Kim et al. | A scalable pub/sub system for ndn | |
| AlShahwan et al. | Providing light weight distributed web services from mobile hosts | |
| US12021921B2 (en) | Data plane reduction for eventing components | |
| CN114945023B (en) | Network connection multiplexing method, device, equipment and medium | |
| Zhan et al. | Distributed enterprise service bus based on JBI | |
| CN114268615B (en) | Service processing method and system based on TCP connection | |
| Serdaroğlu et al. | Effect of Messaging Model on the Reliable Data Transfer Latency in a Fog System | |
| WO2022174675A1 (en) | Computing power information processing method, first network device, and system | |
| Cappa-Banda et al. | Experimenting with a load-aware communication middleware for CPS domains | |
| CN115834670A (en) | Service deployment and inter-service communication method, device, equipment and medium | |
| CN117971516A (en) | Access method, system, equipment and storage medium of message queue | |
| Perera et al. | Common Object Request Broker-based Publisher-Subscriber Middleware for Internet of Things-Edge Computing |
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 |