A cluster load balancing method based on message middleware AOP

Abstract

The present disclosure relates to a cluster load balancing method based on message middleware AOP, which belongs to the field of information processing technology, including: splitting a virtual host: splitting a virtual host into multiple ones at the proxy layer, and storing them on different Broker nodes respectively; information storage: storing all switches under the same virtual host on different Broker nodes respectively; generating a corresponding relationship: setting a corresponding relationship between a switch and the Broker node where the switch is stored; forwarding a request: after receiving an access request, forwarding the request to the corresponding Broker node. The present disclosure can not only solve a series of protocol compatibility problems, but more importantly, it can also make the load borne by each Broker node more balanced, so that under the condition of a large message throughput, the business traffic can be dispersed to multiple Broker nodes, so that multiple Broker nodes can bear the load, thereby achieving a load balancing effect, which is conducive to avoiding excessive load on a certain Broker node.

Description

Technical Field

[0001] The present disclosure relates to the field of information processing technology, and in particular to a cluster load balancing method based on message middleware AOP. Background Art

[0002] AMQP on Pulsar (AOP) is an open source messaging middleware product based on the cloud-native messaging middleware pulsar and compatible with the AMQP message queue protocol.

[0003] AMQP, or Advanced Message Queuing Protocol, is a popular message queuing protocol. Its basic concept is that producers generate data and send it to a designated exchange on the server for storage. The exchange then sends a copy of the message to a bound queue, and consumers pull data from the designated queue to consume from the server. Common AMQP-compatible products include RabbitMQ and AOP.

[0004] Currently, in the message-based middleware AOP, all switches and queues under the same Vhost are centrally stored on a single broker node. All business operations for that Vhost must be completed through the same broker node. Most business systems currently have very high message throughput, and concentrating all business traffic on the same broker node will place a heavy load on the broker node. Summary of the Invention

[0005] The purpose of the present disclosure is to provide a cluster load balancing method based on message middleware AOP to solve the above-mentioned technical problems in related technologies.

[0006] To achieve the above objectives, according to a first aspect of the present disclosure, a cluster load balancing method based on message middleware AOP is provided, comprising the following steps:

[0007] Split virtual hosts: Split the virtual host into multiple ones at the proxy layer and store them on different Broker nodes;

[0008] Information storage: All switches under the same virtual host are stored on different Broker nodes;

[0009] Generate a correspondence: Set the correspondence between the switch and the Broker node where the switch is stored;

[0010] Forwarding request: After receiving an access request, forward the request to the corresponding Broker node.

[0011] As an optional technical solution, the information storage step further includes:

[0012] After all switches under the same virtual host are stored on different Broker nodes, the queue bound to the switch is stored on the Broker node where the switch is stored.

[0013] As an optional technical solution, in the information storage step, all switches under the same virtual host are evenly stored on different Broker nodes;

[0014] As an optional technical solution, in the information storage step, the storage rule of the switch is:

[0015] All switches are evenly stored on different Broker nodes after hash calculation.

[0016] As an optional technical solution, the step of generating the corresponding relationship includes:

[0017] Using the name of the switch, a correspondence between the name of the switch and the Broker node where the switch is stored is generated.

[0018] As an optional technical solution, the method of generating the correspondence between the switch and the Broker node stored in the switch is:

[0019] Using the name of the switch, the index value between the switch name and the Broker node where the switch is stored is generated by taking the remainder of n through the hash function;

[0020] Wherein, n is the number of virtual hosts split in the step of splitting the virtual hosts.

[0021] As an optional technical solution, the cluster load balancing method based on message middleware AOP further includes a step of storing a corresponding relationship, and the stored corresponding relationship includes:

[0022] After completing the step of generating the corresponding relationship, the corresponding relationship obtained through the step of generating the corresponding relationship is stored in the proxy layer.

[0023] As an optional technical solution, in the forwarding request step, when the client requests access to a switch and / or queue, the proxy layer first parses the correspondence between the switch and the Broker node, and then forwards the request to the corresponding Broker node to complete the request operation.

[0024] As an optional technical solution, the step of splitting the virtual hosts further includes: splitting the multiple virtual hosts into multiple ones at the proxy layer, and storing them on different Broker nodes respectively.

[0025] As an optional technical solution, in the forwarding request step, the client accesses the cluster through a proxy layer.

[0026] According to a second aspect of the present disclosure, a cluster load balancing system based on message middleware AOP is further provided. The cluster load balancing method based on message middleware AOP described in the first aspect is applied to any cluster load balancing system based on message middleware AOP, wherein the system includes at least one client, a proxy layer, and multiple Broker nodes;

[0027] The client is used to send access request information to the proxy layer;

[0028] The proxy layer parses the corresponding relationship according to the information, obtains the Broker node requested to be accessed, and forwards the request to the corresponding Broker node.

[0029] According to a third aspect of the present disclosure, a cluster is further provided, wherein the cluster load balancing method based on message middleware AOP described in the first aspect is applied to the cluster, and the cluster includes multiple clients.

[0030] According to a fourth aspect of the present disclosure, a computer program product containing instructions is also provided. When the computer program product is run on a computer, the computer can execute the cluster load balancing method based on message middleware AOP in the present disclosure.

[0031] According to the fifth aspect of the present disclosure, a computer-readable storage medium is also provided, in which instructions are stored. When the instructions are run on a computer, the computer can execute the cluster load balancing method based on message middleware AOP in the present disclosure.

[0032] Through the above technical solution, the virtual host (Vhost) can be disassembled into multiple virtual hosts and distributed on different Broker nodes, and all switches under the same virtual host can be stored on different Broker nodes respectively. In this way, not only can a series of protocol compatibility problems be solved, but more importantly, the load borne by each Broker node can be more balanced. In the case of a large message throughput, the business traffic can be distributed to multiple Broker nodes, so that multiple Broker nodes can bear the load, thereby achieving a load balancing effect, which is conducive to avoiding excessive load on a certain Broker node.

[0033] The cluster load balancing method based on message middleware AOP disclosed in the present invention has at least the following beneficial effects:

[0034] 1. Through the cluster load balancing method based on message middleware AOP disclosed in this invention, the operating pressure of a single virtual host can be distributed to the entire message middleware AOP cluster, achieving cluster load balancing effect, which is conducive to improving the stability and availability of the cluster.

[0035] 2. The cluster load balancing method based on message middleware AOP disclosed in the present invention can be compatible with the message queue protocol of the message middleware, and can effectively reduce the transformation and application work of user migration.

[0036] Other features and advantages of the present disclosure will be described in detail in the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The accompanying drawings are used to provide a further understanding of the present disclosure and constitute a part of the specification. Together with the following detailed description, they are used to explain the present disclosure but do not constitute a limitation of the present disclosure. In the accompanying drawings:

[0038] Figure 1 This is a schematic diagram of the steps of a cluster load balancing method based on message middleware AOP provided by an exemplary embodiment of the present disclosure;

[0039] Figure 2 The figure is a flow chart of a client accessing a queue according to an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0040] The following describes embodiments of the present disclosure in more detail with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.

[0041] It should be understood that the various steps described in the method embodiments of the present disclosure can be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.

[0042] In this disclosure, the terms used, such as "and / or", are merely a description of the association relationship between associated objects, indicating that there may be three types of relationships. For example, a switch and / or a queue may represent three situations, namely: the existence of a switch alone, the existence of a switch and a queue at the same time, and the existence of a queue alone.

[0043] In the specification of the present disclosure, the terms used, such as "first", "second" and "third", etc., are only used to distinguish different objects, or to distinguish different treatments of the same object, rather than to describe the specific order of objects, and do not mean that they have differences in order and importance.

[0044] Furthermore, the terms "including," "having," and any variations thereof, as used in the description of this disclosure are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to the process, method, product, or apparatus.

[0045] It should be noted that in the embodiments of the present disclosure, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present disclosure should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0046] The most critical inventive concept of the present disclosure is that: in the usage scenario where the traffic of the business system is concentrated on one or more virtual hosts, the virtual host (Vhost) can be disassembled (mapped) into multiple virtual hosts, and these can be dispersed on different Broker nodes, and all switches under the same virtual host can be stored on different Broker nodes respectively. In this way, not only can a series of protocol compatibility problems be solved, but more importantly, the load borne by each Broker node can be more balanced, so that under the condition of a larger message throughput, the business traffic can be dispersed to multiple Broker nodes, so that multiple Broker nodes can bear the load, thereby achieving the effect of load balancing of the entire message middleware cluster, which is conducive to avoiding excessive load on a certain Broker node.

[0047] like Figures 1 to 2As shown, according to the first aspect of the present disclosure, a cluster load balancing method based on message middleware AOP is provided, including the following steps: splitting the virtual host, information storage, generating a corresponding relationship and forwarding a request; wherein, the step of splitting the virtual host includes: splitting the virtual host into multiple ones at the proxy layer, and storing them on different Broker nodes respectively; the step of storing information includes: storing all switches under the same virtual host on different Broker nodes respectively; the step of generating a corresponding relationship includes: setting a corresponding relationship between the switch and the Broker node where the switch is stored; the step of forwarding the request includes: after receiving an access request, forwarding the request to the corresponding Broker node.

[0048] Through the above technical solution, the virtual host (Vhost) can be disassembled into multiple virtual hosts and distributed on different Broker nodes, and all switches under the same virtual host can be stored on different Broker nodes respectively. In this way, not only can a series of protocol compatibility problems be solved, but more importantly, the load borne by each Broker node can be more balanced. In the case of a large message throughput, the business traffic can be distributed to multiple Broker nodes, so that multiple Broker nodes can bear the load, thereby achieving a load balancing effect, which is conducive to avoiding excessive load on a certain Broker node.

[0049] In this disclosure, the mutual terminology of the message middleware AMQP that needs to be explained includes:

[0050] The Advanced Message Queuing Protocol (AMQP) is an application-layer standard for providing unified messaging services. It's an open standard for application-layer protocols designed for message-oriented middleware. Clients and message-oriented middleware based on this protocol can exchange messages without being restricted by different client / middleware products or development languages.

[0051] A virtual host (Vhost) is a collection of switches, message queues, and related objects. A virtual host is an independent server domain that shares the same authentication and encryption environment. A client can select a virtual host after logging into the server to use an application.

[0052] A producer (ie, the producer mentioned in the background technology, English name: Producer) is a client application that publishes messages to an exchange.

[0053] A consumer (ie, the consumer mentioned in the background technology, the English name is: Consumer) refers to a client application that requests messages from a message queue.

[0054] The server (the server mentioned in the background technology, English name: Server) refers to the process that accepts client connections and implements AMQP message queue and routing functions.

[0055] Client: The initiator of an AMQP connection or session. AMQP is asymmetric; the client produces and consumes messages, while the server stores and routes these messages.

[0056] Exchange: An entity in the server that receives messages from producers and routes them to queues in the server.

[0057] Channel: An independent bidirectional data flow channel in a multiplexed connection. It provides the physical transmission medium for the session.

[0058] In addition, it is understandable that the cluster load balancing method based on the message middleware AOP disclosed in the present invention also requires the AMQP message transmission protocol to solve the following problems:

[0059] First, the Broker node redirection problem: In the existing related technologies, one virtual host (Vhost) corresponds to one Broker node, while the technical solution disclosed in this disclosure requires one virtual host (Vhost) to correspond to multiple Broker nodes.

[0060] Second, the problem of using multiple topics on a single channel: In existing related technologies, the message transmission protocol allows the client to use multiple topics on a single channel, which means that a single channel may need to connect to multiple Broker nodes to send requests.

[0061] In an exemplary embodiment of the present disclosure, the information storage step of the present disclosure may further include: after storing all switches under the same virtual host on different Broker nodes respectively, storing the queue bound to the switch on the Broker node where the switch is stored.

[0062] This not only allows queues to be effectively stored on the corresponding broker nodes, but also ensures a one-to-one correspondence between the queue, the switch bound to the queue, and the broker node that stores the queue and switch. This, on the one hand, allows for an association between the queue, switch, and corresponding broker node, and on the other hand, it also avoids the problem of information loss during storage to a certain extent.

[0063] In an exemplary embodiment of the present disclosure, in the information storage step of the present disclosure, all switches under the same virtual host can be evenly stored on different Broker nodes.

[0064] This helps all Broker nodes to bear the pressure of business traffic more evenly in the case of huge message throughput, and all Broker nodes share the load more evenly.

[0065] In an exemplary embodiment of the present disclosure, in the information storage step of the present disclosure, the storage rule of the switches is: all switches are evenly stored on different Broker nodes after hash calculation.

[0066] In this way, using hash calculations can ensure that all switches are evenly stored on different Broker nodes. For example, you can choose a consistent hashing algorithm, which is a modified version of the ordinary modulo hashing algorithm. The function calculation method of the consistent hashing algorithm remains unchanged, but it replaces the ordinary linear hashing space by constructing a circular hash space. This is because in a distributed system, each node may fail, and new nodes may be added dynamically. Therefore, a consistent hashing algorithm can be used to ensure the consistency of the system.

[0067] In an exemplary embodiment of the present disclosure, the step of generating a corresponding relationship includes: using the name of the switch to generate a corresponding relationship between the name of the switch and the Broker node stored in the switch.

[0068] In this way, a unique and simple correspondence can be established between the switch and the Broker node where the switch is stored, which is beneficial for the client to quickly and accurately forward the access request to the corresponding Broker node when requesting access to a certain Broker node, thereby reducing network interaction time and improving system efficiency.

[0069] In an exemplary embodiment of the present disclosure, the method of generating the correspondence between the switch and the Broker node stored in the switch is: using the name of the switch, generating an index value between the switch name and the Broker node stored in the switch by taking the modulus n of a hash function;

[0070] Wherein, n is the number of virtual hosts split in the step of splitting the virtual hosts.

[0071] In this way, all switches can be accurately and uniquely matched with Broker nodes, and the hash remainder algorithm used by the switch is very simple, which can effectively improve the system operation efficiency.

[0072] In an exemplary embodiment of the present disclosure, the cluster load balancing method based on message middleware AOP of the present disclosure also includes a corresponding relationship storage step, and the corresponding relationship storage includes: after completing the corresponding relationship generation step, storing the corresponding relationship obtained through the corresponding relationship generation step in the proxy layer.

[0073] In this way, storing the generated correspondence in the proxy layer can facilitate the proxy layer to quickly parse the correspondence between the switch (or queue) and the Broker node, and can quickly forward the access request information to the corresponding Broker node to complete the work quickly.

[0074] In an exemplary embodiment of the present disclosure, in the forwarding request step of the present disclosure, when the client requests access to a certain switch and / or queue, the proxy layer first parses the correspondence between the switch and the Broker node, and then forwards the request to the corresponding Broker node to complete the request operation.

[0075] In an exemplary embodiment of the present disclosure, the step of splitting the virtual hosts may further include: splitting the multiple virtual hosts into multiple ones at the proxy layer, and storing them on different Broker nodes respectively.

[0076] In this way, the cluster load balancing method based on message middleware AOP disclosed in the present invention can enable multiple virtual hosts to be split into multiple, which is beneficial for all Broker nodes corresponding to all virtual hosts in the entire cluster to achieve load balancing effect.

[0077] In an exemplary embodiment of the present disclosure, in the forwarding request step of the present disclosure, the client accesses the cluster through a proxy layer.

[0078] like Figure 2 As shown, taking a specific embodiment as an example, that is, taking a client sending a request that includes a process that requires access to three queues as an example, the process of the cluster load balancing method based on message middleware AOP of the present disclosure is explained. However, it should be understood that this embodiment is only an exemplary implementation method, which is intended to facilitate understanding and does not limit the technical solution of the present disclosure. It should not be understood that this implementation method is the only implementation method of the present application.

[0079] First, in the first step, assume that the virtual host (vhost) is split into three, and name these three virtual hosts: the first virtual subhost vhost1, the second virtual subhost vhost2, and the third virtual subhost vhost3, and store the first virtual subhost vhost1, the second virtual subhost vhost2, and the third virtual subhost vhost3 on the first node Broker1, the second node Broker2, and the third node Broker3 respectively.

[0080] In the second step, assume that there are three switches, and name these three switches as the first switch E1, the second switch E2 and the third switch E3 respectively. Use the name of the first switch (for example, E1, E2 and E3) and the algorithm modulo 3 of the hash function to obtain the index value (that is, the corresponding relationship described above) and store it on the corresponding first node Broker1, the second node Broker2 and the third node Broker3; at the same time, the first queue q1, the second queue q2 and the third queue q3 corresponding to the three switches are stored on the corresponding Broker nodes following the bound switches, and the proxy layer also stores the corresponding relationship between the switches and the Broker nodes.

[0081] In the third step, the client accesses the cluster through the proxy layer. When it needs to access a switch or queue, the proxy layer uses the correspondence between the switch and the Broker node to forward the access request to the corresponding Broker node to complete the request operation.

[0082] It can be understood that the present disclosure is aimed at the usage scenario where the traffic of the business system is concentrated on one or more virtual hosts. By mapping the virtual host into multiple virtual hosts and distributing them in multiple Broker nodes, the entire message middleware cluster can achieve a debt-balanced effect.

[0083] According to a second aspect of the present disclosure, a cluster load balancing system based on message middleware AOP is further provided. The cluster load balancing method based on message middleware AOP described in the first aspect is applied to any cluster load balancing system based on message middleware AOP, wherein the system includes at least one client, a proxy layer, and multiple Broker nodes;

[0084] The client is used to send access request information to the proxy layer;

[0085] The proxy layer parses the corresponding relationship according to the information, obtains the Broker node requested to be accessed, and forwards the request to the corresponding Broker node.

[0086] In this way, through the cluster load balancing system based on message middleware AOP disclosed in the present invention, in the usage scenario where the traffic of the business system is concentrated on one or more virtual hosts, the virtual host (Vhost) can be disassembled (mapped) into multiple virtual hosts, and they can be dispersed on different Broker nodes, and all switches under the same virtual host can be stored on different Broker nodes respectively. In this way, not only can a series of protocol compatibility problems be solved, but more importantly, the load borne by each Broker node can be more balanced, so that under the condition of larger message throughput, the business traffic can be dispersed to multiple Broker nodes, so that multiple Broker nodes can bear the load, thereby achieving the effect of load balancing of the entire message middleware cluster, which is conducive to avoiding excessive load on a certain Broker node.

[0087] According to a third aspect of the present disclosure, a cluster is further provided, wherein the cluster load balancing method based on message middleware AOP in the first aspect of the present disclosure is applied to the cluster, and the cluster includes multiple clients.

[0088] In this way, the load of the message middleware in the cluster disclosed in the present invention can be evenly distributed to multiple Broker nodes, which is beneficial to avoid excessive load on a certain Broker node.

[0089] According to a fourth aspect of the present disclosure, a computer program product containing instructions is also provided. When the computer program product is run on a computer, the computer can execute the cluster load balancing method based on message middleware AOP in the present disclosure.

[0090] According to the fifth aspect of the present disclosure, a computer-readable storage medium is also provided, in which instructions are stored. When the instructions are run on a computer, the computer can execute the cluster load balancing method based on message middleware AOP in the present disclosure.

[0091] Among them, the computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a register, a hard disk, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above, or any other form of computer-readable storage medium known in the art. An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an application-specific integrated circuit (ASIC). In the present disclosure, a computer readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0092] In the embodiments provided in the present disclosure, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0093] In this disclosure, units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected based on actual needs to achieve the objectives of this embodiment.

[0094] The above description is merely a preferred embodiment of the present disclosure and an illustration of the technical principles employed. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by the specific combination of the above-mentioned technical features, but also includes other technical solutions formed by any combination of the above-mentioned technical features or their equivalents without departing from the above-mentioned disclosed concepts. For example, a technical solution formed by replacing the above-mentioned features with (but not limited to) technical features with similar functions disclosed in this disclosure.

[0095] It should also be noted that the various specific technical features described in the above specific embodiments can be combined in any appropriate manner without contradiction. In order to avoid unnecessary repetition, the present disclosure will not further describe various possible combinations.

[0096] In addition, although each operation is described in a specific order, this should not be understood as requiring these operations to be performed in the specific order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details have been included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination mode.

[0097] In addition, the various embodiments of the present disclosure may be arbitrarily combined, and as long as they do not violate the ideas of the present disclosure, they should also be regarded as the contents disclosed by the present disclosure. Although the subject matter has been described in the language of specific method logical actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. On the contrary, the specific features and actions described above are merely example forms of implementing the claims. Regarding the device in the above embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment of the method, and will not be elaborated here.

Claims

1. A cluster load balancing method based on message middleware AOP, characterized in that: The steps include: Split virtual hosts: Split the virtual host into multiple ones at the proxy layer and store them on different Broker nodes; Information storage: All switches under the same virtual host are stored on different Broker nodes; Generate a correspondence: Set the correspondence between the switch and the Broker node where the switch is stored; Forwarding request: After receiving an access request, forward the request to the corresponding Broker node.

2. The cluster load balancing method based on message middleware AOP according to claim 1 is characterized in that: The information storage step further includes: After all switches under the same virtual host are stored on different Broker nodes, the queue bound to the switch is stored on the Broker node where the switch is stored.

3. The cluster load balancing method based on message middleware AOP according to claim 1 is characterized in that: In the information storage step, all switches under the same virtual host are evenly stored on different Broker nodes.

4. The cluster load balancing method based on message middleware AOP according to claim 1 is characterized in that: In the information storage step, the storage rules of the switch are: All switches are evenly stored on different Broker nodes after hash calculation.

5. The cluster load balancing method based on message middleware AOP according to claim 1 is characterized in that: The step of generating a corresponding relationship includes: Using the name of the switch, a correspondence between the name of the switch and the Broker node where the switch is stored is generated.

6. The cluster load balancing method based on message middleware AOP according to claim 5 is characterized in that: The method of generating the correspondence between the switch and the Broker node stored in the switch is: Using the name of the switch, the index value between the switch name and the Broker node where the switch is stored is generated by taking the remainder of n through the hash function; Wherein, n is the number of virtual hosts split in the step of splitting the virtual hosts.

7. The cluster load balancing method based on message middleware AOP according to claim 1 is characterized in that: The cluster load balancing method based on message middleware AOP further includes a step of storing corresponding relationships, and the storing corresponding relationships includes: After completing the step of generating the corresponding relationship, the corresponding relationship obtained through the step of generating the corresponding relationship is stored in the proxy layer.

8. The cluster load balancing method based on message middleware AOP according to claim 1 is characterized in that: In the forwarding request step, when the client requests to access a switch and / or queue, the proxy layer first parses the correspondence between the switch and the Broker node, and then forwards the request to the corresponding Broker node to complete the request operation.

9. The cluster load balancing method based on message middleware AOP according to any one of claims 1 to 8, characterized in that: The step of splitting the virtual hosts also includes: splitting the multiple virtual hosts into multiple ones at the proxy layer, and storing them on different Broker nodes respectively.

10. The cluster load balancing method based on message middleware AOP according to any one of claims 1 to 8, characterized in that: In the forwarding request step, the client accesses the cluster through the proxy layer.

Images