CN109257435B - Communication system of multi-instance multi-subsystem application based on message middleware - Google Patents
Communication system of multi-instance multi-subsystem application based on message middleware Download PDFInfo
- Publication number
- CN109257435B CN109257435B CN201811229698.9A CN201811229698A CN109257435B CN 109257435 B CN109257435 B CN 109257435B CN 201811229698 A CN201811229698 A CN 201811229698A CN 109257435 B CN109257435 B CN 109257435B
- Authority
- CN
- China
- Prior art keywords
- application
- manager
- subsystem
- instance
- gateway
- 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.)
- Active
Links
- 238000004891 communication Methods 0.000 title claims abstract description 57
- 238000000034 method Methods 0.000 abstract description 15
- 238000012545 processing Methods 0.000 description 15
- 230000003993 interaction Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 6
- 230000005540 biological transmission Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 230000010365 information processing Effects 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 238000011160 research Methods 0.000 description 2
- 230000003111 delayed effect Effects 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
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/2866—Architectures; Arrangements
- H04L67/288—Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/042—Network management architectures or arrangements comprising distributed management centres cooperatively managing the network
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 communication system of the message-middleware-based multi-instance multi-subsystem application comprises a first subsystem, a second subsystem and a third subsystem, wherein the first subsystem comprises an external system and a plurality of application instances, the first subsystem further comprises a plurality of application node managers, and the number of the application node managers is more than 1; one application node manager is correspondingly connected with at least one application instance; the plurality of application node managers are respectively connected with the external system. The application increases the number of the application node managers, namely increases the use resources of the MQ managers, wherein one application node manager is correspondingly connected with at least one application instance, and preferably, a method of the MQ manager can be respectively provided for each application instance, so that the MQ communication resources between the application instances cannot be mutually occupied, the application instances cannot be mutually influenced, and the problem of a certain MQ manager cannot influence all the application instances.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a communication system for multi-instance and multi-subsystem applications based on message middleware.
Background
In an application system, a message middleware is often used for communication between applications.
The message middleware is a communication technology for data transmission between applications, and is a communication technology distinguished from remote procedure calls. The Message middleware products on the market at present mainly comprise Kafka, RabbitMQ, RockettMQ, ActiveMQ, Joram, HornetQ, OpenMQ, IBM WebSphere MQ (Message Queue) and the like. The message middleware simplifies data transmission among application programs, provides a uniform communication standard, enables messages to be transmitted safely and reliably among different systems, and ensures reliable and cross-platform information transmission and data exchange under a distributed network environment.
As shown in fig. 1, in the current messaging middleware based application system communication architecture, multiple application instances of the application system interact with external systems by connecting an MQ manager. Wherein all interactions with external systems and internal information processing are managed through the MQ manager.
Specifically, the interaction with the external system mainly includes: defining a sending channel, a receiving channel, a transmission queue and a remote queue related to an external system. The application instance places the return message to a remote queue and the MQ manager automatically sends the return message to the external system. The internal information processing mainly comprises: (1) a normal queue for application instance read messages is defined. The external system sends the message to a common queue of the MQ manager, and the application instance automatically reads the message from the common queue for processing; (2) communication between application instances is realized by defining topic on the MQ manager, when one application instance modifies the content of the common part, the application instance sends topic to the MQ manager, and other instances receive the topic content from the MQ manager, so as to correspondingly process the modified common part.
However, the applicant of the present application noticed that the currently existing messaging middleware based application system communication architecture shown in fig. 1 has at least the following problems:
(1) the limited use of resources by a single MQ manager results in resource crowding among different application instances.
For example, a single MQ manager may provide a limited number of connection paths, and an application instance may have many threads to connect to the MQ manager, and when multiple application instances are connected, the maximum number of connection paths of the single MQ manager may be easily exceeded, and at this time, the multiple application instances may possibly have a problem of crowding the connection paths with each other.
For another example, the processing process that a single MQ manager can start is limited, and the traffic volume of some areas may far exceed the traffic volume of other areas, so that more messages are sent and received by application instances corresponding to these areas, and when the single MQ manager cannot process the messages, the messages of other application instances can only be queued for waiting, and cannot be processed in time later, which cannot be tolerated for some service transactions with strong real-time requirements, and timeout error reporting is easy to occur frequently.
(2) Problems with one application instance can easily affect other application instances.
When a problem occurs in one application instance, the MQ manager may need to be stopped to match debugging and find the reason of the problem, and during the period of troubleshooting, other application instances cannot normally operate to provide the application service.
(3) Problems with the MQ manager can affect the operation of all application instances.
When problems arise with the MQ manager itself, the operation of all application instances can be affected.
Disclosure of Invention
In view of this, the present application provides a communication system of multi-instance multi-subsystem application based on message middleware, which is used to solve the problems that MQ communication resources between application instances occupy each other, the application instances affect each other, and the MQ manager affects all the application instances in the existing communication architecture of the application system based on message middleware. The technical scheme is as follows:
the invention provides a communication system of multi-instance multi-subsystem application based on message middleware, which comprises a first subsystem, a second subsystem and a plurality of application nodes, wherein the first subsystem comprises an external system and a plurality of application instances, the first subsystem further comprises a plurality of application node managers, and the number of the application node managers is more than 1;
one application node manager is correspondingly connected with at least one application instance;
the plurality of application node managers are respectively connected with the external system.
Optionally, the number of the application node managers is equal to the number of the application instances, and the plurality of application node managers are connected with the plurality of application instances in a one-to-one correspondence manner.
Optionally, the first subsystem further comprises: an external gateway manager and an application gateway manager; wherein,
the external gateway manager is connected with the external system;
the application gateway manager is connected with the external gateway manager, and the application gateway manager is respectively connected with each application node manager.
Optionally, the communications system further comprises a shared MQ manager and a second subsystem; wherein,
the architecture of the second subsystem is the same as that of the first subsystem, and an application gateway manager in the second subsystem and an application gateway manager in the first subsystem are respectively connected with the shared MQ manager;
the shared MQ manager is used for realizing topic switching among subsystems.
Optionally, the first subsystem further comprises: a first service system;
the first service system comprises an application gateway manager, an application node manager and an application instance, and the architecture of the first service system is the same as the connection architecture of the original application gateway manager, the original application node manager and the original application instance in the first subsystem.
Optionally, the second subsystem further comprises: a second service system;
the second service system comprises an application gateway manager, an application node manager and an application instance, and the architecture of the second service system is the same as the connection architecture of the original application gateway manager, the original application node manager and the original application instance in the second subsystem.
Optionally, the communication system further comprises: and the shared MQ manager is respectively connected with the application gateway manager in the first service system and the application gateway manager in the second service system.
Optionally, the number of the shared MQ managers respectively connected to the application gateway manager in the second subsystem and the application gateway manager in the first subsystem is greater than 1;
the number of the shared MQ managers respectively connected with the application gateway manager in the first service system and the application gateway manager in the second service system is more than 1.
In the communication system of the message-middleware-based multi-instance multi-subsystem application, the first subsystem comprises an external system, a plurality of application instances and a plurality of application node managers, and the application node managers are respectively connected with the external system. In the application, the number of the application node managers (namely, the MQ managers) is greater than 1, compared with a mode that a plurality of application instances interact with an external system by connecting one MQ manager in the prior art, the application increases the number of the application node managers, namely, the used resources of the MQ managers are increased, wherein one application node manager is correspondingly connected with at least one application instance, and preferably, a method of one MQ manager can be respectively provided for each application instance, so that MQ communication resources between the application instances cannot be mutually occupied, the application instances cannot be mutually influenced, and problems of one MQ manager cannot influence all the application instances.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a diagram illustrating a communication architecture of an application system based on message middleware in the prior art;
fig. 2 is a schematic structural diagram of a communication system of a message-middleware-based multi-instance multi-subsystem application provided in the present application;
FIG. 3 is a block diagram of another message-middleware based communication system for multi-instance multi-subsystem applications provided herein;
fig. 4 is a schematic structural diagram of a communication system of yet another message-middleware-based multi-instance multi-subsystem application provided in the present application;
fig. 5 is a schematic structural diagram of a communication system of yet another message-middleware-based multi-instance multi-subsystem application provided in the present application;
fig. 6 is a schematic structural diagram of a communication system of yet another message-middleware-based multi-instance multi-subsystem application provided in the present application.
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.
The services processed by the application system may be distributed in different areas (e.g. asia, europe, africa, america, etc.), and the differences between different areas may be relatively large (e.g. time difference, when the application system is desired to be upgraded, it is likely that the services in a certain area are open, and it is often not suitable for the actual situation of the services to make all areas shut down for upgrading the system). Therefore, in the development of software systems, people often divide the application systems into different application instances according to different areas. Although the application system is divided into different application instances, it is not possible to prepare a set of data (e.g., a database table) for each application instance, and thus different application instances share a common set of data. When one application instance modifies the public part of the shared data, other application instances need to be informed so that the other application instances can timely perform corresponding processing.
On the other hand, the service types of the application systems may be various. The difference between different types of services may be relatively large (for example, the public service and the private service in a bank, the public service of the bank may be only one hundred thousand, but the private service of the bank may reach over ten million or even over one hundred million). Although different types of services, they may share some common data of the application system (e.g., a bank's credit, having a public credit, and also having a private credit, but the total credit of a bank is fixed over a period of time, and the total credit and private credit added up should not exceed the total credit of the bank.
However, the existing communication architecture based on message middleware often cannot meet the requirement of multi-instance multi-subsystem application, and the applicant of the present application mainly studies from the following aspects:
1) in the multi-instance multi-subsystem application, the service is different between different application instances and between different subsystems. The general communication architecture based on the message middleware cannot well handle the situation of multiple instances and multiple subsystems, the situation that resources between different application instances and between different subsystems are mutually occupied is easy to occur, and the service of the occupied application instances or subsystems can not be processed late, which is intolerable for some service transactions with strong real-time requirements. Therefore, there is a need to solve the problem of how to avoid resource occupation between application instances and subsystems in multi-instance and multi-subsystem applications.
2) In multi-instance multi-subsystem applications, different application instances and different subsystems often need to share a part of data, so that communication is needed among the application instances and the subsystems, and each application instance and each subsystem can know the latest condition of shared data in time so as to perform corresponding processing. Therefore, there is a need to solve the problem of how to communicate between application instances and subsystems in multi-instance and multi-subsystem applications.
3) In the multi-instance multi-subsystem application, each subsystem generally has a plurality of application instances, each application instance interacts with an external system, and if a uniform interaction mode does not exist, a new interaction mode with the external system needs to be added for each application instance added to the subsystem, which brings inconvenience to the development of the application system. Therefore, a problem of how to provide uniform interaction between application instances in multi-instance multi-subsystem applications is currently needed to be solved.
4) If the application instance only has a single service, when the service is hung up, the service of the application instance cannot be provided, which is not favorable for the stability of the system. At the same time, the processing power of the application instance of a single service is limited. Therefore, there is a need to solve the problem of how multi-instance multi-subsystem applications enhance the robustness and processing power of the system.
In view of the above, the present application provides communication architectures for message-middleware based multi-instance multi-subsystem applications in a variety of different configurations. In the following, the applicant will in turn describe in detail a communication system based on message middleware multi-instance multi-subsystem application in various structural forms provided by the present application.
Example one
Firstly, aiming at the existing message middleware based application system communication architecture, a mode that a plurality of application instances interact with an external system by connecting an MQ manager is adopted, and the problem that the resource utilization of a single MQ manager causes that different application instances mutually occupy the resource, the application instances mutually influence, and the MQ manager generates a problem and can influence all the application instances, the application proposes the message middleware based multi-instance multi-subsystem application communication system shown in FIG. 2, which comprises a first subsystem, wherein the first subsystem comprises an external system 100 and a plurality of application instances 200, in particular, the first subsystem also comprises a plurality of application node managers 300, and the number of the application node managers is more than 1. It should be noted that, in the embodiment of the present application, the application node manager 300 is substantially an MQ manager.
In the embodiment of the present application, the number of the application node managers 300 is greater than 1, and compared with a manner in which a plurality of application instances interact with an external system by connecting one MQ manager in the prior art, the present application increases the number of the application node managers 300, that is, increases the use resources of the MQ manager.
Specifically, in the embodiment of the present application, one application node manager 300 is correspondingly connected to at least one application instance 200, and the plurality of application node managers 300 are respectively connected to the external system 100.
As a preferred embodiment of the present application, as shown in fig. 3, the number of the application node managers 300 in the present application may be equal to the number of the application instances 200, that is, the application node managers 300 are connected to the application instances 200 in a one-to-one correspondence manner. By providing an MQ manager for each application instance, MQ communication resources between the application instances cannot be crowded to each other, the application instances cannot be influenced by each other, and a problem of one MQ manager cannot influence all the application instances.
Example two
Further, the applicant of the present application notes that although the first embodiment of the present application can solve the problems that MQ communication resources between application instances crowd each other, the application instances affect each other, and a problem of the MQ manager affects all application instances, the first embodiment of the present application has some problems:
(1) since the application node managers 300 are independent of each other, when a certain application instance 200 changes data of a common part in an application system, other application instances 200 cannot know;
(2) each time a new application instance 200 is added, the interaction mode between the corresponding application node manager 300 and the external system 100 needs to be configured for the new application instance 200.
To further solve the above problems (1) and (2), as shown in fig. 4, the present application proposes another communication system based on message middleware for multi-instance and multi-subsystem application, where the first subsystem in the communication system further includes: an extranet gateway manager 400 and an application gateway manager 500. Wherein,
the outbound gateway manager 400 is connected to the external system 100.
The application gateway manager 500 is connected to the extranet gateway manager 400, and the application gateway manager 500 is simultaneously connected to each of the application node managers 300, respectively.
Compared with the first embodiment, in the second embodiment of the present application, an application gateway manager 500 is added, the application gateway manager 500 is connected to each application node manager 300 to form an MQ cluster, the application gateway manager 500 is used as a warehouse (note book) of the whole cluster to record information of the whole cluster, and topic of the cluster is defined in the application gateway manager 500. Meanwhile, an external gateway manager 400 is added in the embodiment of the present application, the external gateway manager 400 is connected to the application gateway manager 500, and also belongs to the MQ cluster, all interactions with the external system 100 are defined in the external gateway manager 400, and the external gateway manager 400 provides unified interactions with the external system 100.
In the second embodiment of the present application, the topic of the cluster is defined in the application gateway manager 500, each application instance 200 is connected to the application gateway manager 500 through the application node manager 300, when the application gateway manager 500 receives the topic, the topic is forwarded to each application node manager 300, and each corresponding application instance 200 receives the topic, so that each application instance 200 can communicate with each other.
The external information of the whole cluster is defined on the external gateway manager 400, so that no matter how many application examples 200 exist, the application system only needs to provide the interactive information managed by the external gateway to all external systems 100, meanwhile, the interactive information of all external systems 100 only needs to be defined on the external gateway manager 400, the messages sent to the application system by all external systems 100 only need to be sent to the external gateway manager 400, and the external gateway manager 400 searches the application gateway manager 500 for an actual destination to carry out internal forwarding.
EXAMPLE III
After the applicant researches a communication system of a message-middleware-based multi-instance multi-subsystem application provided by the second embodiment of the present application, the second embodiment further has the following problems:
since all kinds of services are processed in one application system, for services with a relatively large degree of distinction, a large amount of services easily occupy processing resources of a small amount of services, so that the small amount of services cannot be processed in a delayed manner, which is a condition that a transaction is overtime easily and frequently occurs for certain service transactions with relatively strong real-time requirements.
In order to solve this problem, the present application further proposes a method for dividing an application system into several subsystems according to services with relatively large category distinctiveness, that is, a communication system may include a plurality of subsystems, such as a first subsystem 10, a second subsystem 20, and the like.
However, after the application system is divided into several subsystems, the several subsystems are a set of common data in the common application system, and when a certain application instance in a certain subsystem modifies the common data of the application system, it is necessary to notify not only other application instances of the subsystem but also application instances of other subsystems.
In this regard, as shown in fig. 5, the communication system for the message-middleware based multi-instance multi-subsystem application provided by the present application may further include a shared MQ manager 600.
In the embodiment of the present application, the architecture of the second subsystem 20 is the same as that of the first subsystem 10, and the application gateway manager in the second subsystem 20 and the application gateway manager in the first subsystem 10 are respectively connected to the shared MQ manager 600.
The embodiment of the application constructs the shared MQ manager 600 among a plurality of subsystems, and the topic of a certain subsystem can be forwarded to other subsystems through the shared MQ manager 600, so that the communication mode of a single subsystem can be used in the plurality of subsystems without modification.
Specifically, in the embodiment of the present application, a shared MQ manager 600 is established among multiple subsystems, a sub (sub-topic) of topic of a subsystem is defined in the application gateway manager 500 of the subsystem, points to an alias in the shared MQ manager 600, an alias is defined on the shared MQ manager 600, and points to topic on the application gateway manager 500 of another subsystem. Thus, for a topic sent on one subsystem, not only all application instances 200 on that subsystem will be received, but also all application instances of another subsystem.
Referring to fig. 5, the first subsystem 10 will be described as subsystem a, and the second subsystem 20 will be described as subsystem B.
Subsystem a and subsystem B correspond to MQ cluster a and MQ cluster B, respectively, to which shared MQ manager 1 belongs simultaneously (by defining itself as belonging to both clusters on shared MQ manager 1). The sub-topic sub of topoc _ a of cluster a is defined on application gateway manager a of cluster a pointing to an alias in shared MQ manager 1, the alias is defined in shared MQ manager 1 pointing to topoc _ B in cluster B. (shared MQ manager 1 can see topic of both clusters because it belongs to both clusters, and no topic undefined condition occurs).
Thus, the topic of the cluster A can be forwarded to the cluster B, and similarly, if the topic in the cluster B needs to be forwarded to the cluster A, the same operation is only needed. The following practical operation steps are described by taking an IBM MQ as an example:
the application gateway manager on subsystem a defines the topic of subsystem a:
DEFINE TOPIC(TOPIC_A)TOPICSTR(/flms/parcache)CLUSTER(FLMSCLUS)PUB(ASPARENT)SUB(ENABLED)WILDCARD(PASSTHRU)；
SUB defining the TOPIC at the same time, points to the alias of begin.a.to.b. DEFINE SUB (SUB _ top _ a) TOPICOBJ (top _ a) DEST (alias of top.a.to.b) on the shared MQ manager 1;
define the alias. topic.a.to.b on the shared MQ manager 1, execute to the topic on the application gateway manager on subsystem B
DEFINE QALIAS(ALIAS.TOPIC.A.TO.B)TARGET(TOPIC_B)CLUSTER(FLMSCLUS)TARGTYPE(TOPIC)REPLACE；
Application gateway manager on subsystem B defines the topic of subsystem B
DEFINE TOPIC(TOPIC_B)TOPICSTR(/flms/parcache_b)CLUSTER(FLMSCLUS_B)PUB(ASPARENT)SUB(ENABLED)WILDCARD(PASSTHRU)。
Example four
After the applicant researches a communication system of the message-middleware-based multi-instance multi-subsystem application provided by the third embodiment, the third embodiment has the following problems:
taking fig. 5 as an example, if the application node manager A3 hangs up in fig. 5 or the application instance A3 hangs up, the traffic of the application instance A3 has no corresponding service to handle. Obviously, the processing power of the application instance of a single service is limited, and there is a need to increase the robustness of the system and to increase the processing power of the system.
In view of this, as shown in fig. 6, in the present application, on the basis of fig. 5, the first subsystem may further include a first service system 700, where the first service system 700 includes an application gateway manager, an application node manager, and an application instance, and an architecture of the first service system 700 is the same as a connection architecture of the application gateway manager, the application node manager, and the application instance existing in the first subsystem.
Taking fig. 6 as an example, an original application gateway manager in the first subsystem is an application gateway manager a1, the original application node manager includes an application node manager a1_1, an application node manager a2_1, an application node manager A3_1, and an application node manager a4_1, and an original application example includes: the application instance a1_1 connected to the application node manager a1_1, the application instance a2_1 connected to the application node manager a2_1, the application instance A3_1 connected to the application node manager A3_1, and the application instance a4_1 connected to the application node manager a4_1 are corresponded.
In order to increase the robustness of the system and improve the processing capacity of the system, the first service system 700 is provided in the first subsystem, and the first service system 700 includes an application gateway manager a2, an application node manager a1_2, an application node manager a2_2, an application node manager A3_2, an application node manager a4_2, and an application instance a1_2, an application instance a2_2, an application instance A3_2, and an application instance a4_2 that are respectively connected to the application node manager a1_2, the application node manager a2_2, the application node manager A3_2, the application node manager a4_ 2.
Specifically, in the embodiment of the present invention, the connection architectures of the application gateway manager a2, the application node manager a1_2, the application node manager a2_2, the application node manager A3_2, the application node manager a4_2, and the application instance a1_2, the application instance a2_2, the application instance A3_2, and the application instance a4_2 in the first service system 700 are the same as the connection architectures of the application gateway manager a1, the application node manager a1_1, the application node manager a2_1, the application node manager A3_1, and the application node manager a4_1, and the application instance a1_1, the application instance a2_1, the application instance A3_1, and the application instance a4_1 existing in the first subsystem.
The application example A1_1 and the application example A2_1 are different application examples on the same machine, the application example A1_1 and the application example A1_2 are the same application example on different machines, and other application examples are similar. In practical applications, taking the application instance a1_1 as an example, when the application instance a1_1 hangs down or the application node manager a1_1 connected to the application instance a1_1 hangs down, the embodiment of the present invention may continue to provide services by the application instance a1_2 or continue to provide services by the application node manager a1_2, thereby ensuring the robustness of the system and improving the processing capability of the system.
Further, the second subsystem in the embodiment of the present invention may further include: and a second service system 800, where the second service system 800 includes an application gateway manager, an application node manager, and an application instance, and the architecture of the second service system 800 is the same as the connection architecture of the application gateway manager, the application node manager, and the application instance existing in the second subsystem.
Still taking fig. 6 as an example, the original application gateway manager in the second subsystem is the application gateway manager B1, the original application node manager includes the application node manager B1_1, the application node manager B2_1, the application node manager B3_1, and the application node manager B4_1, and the original application example includes: the application instance B1_1 connected to the application node manager B1_1, the application instance B2_1 connected to the application node manager B2_1, the application instance B3_1 connected to the application node manager B3_1, and the application instance B4_1 connected to the application node manager B4_1 are corresponded.
In order to increase the robustness of the system and improve the processing capacity of the system, the second service system 800 is provided in the second subsystem, and the second service system 800 includes an application gateway manager B2, an application node manager B1_2, an application node manager B2_2, an application node manager B3_2, an application node manager B4_2, and an application instance B1_2, an application instance B2_2, an application instance B3_2, and an application instance B4_2 that are respectively connected to the application node manager B1_2, the application node manager B2_2, the application node manager B3_2, and the application node manager B4_ 2.
Specifically, in the embodiment of the present invention, the connection architecture of the application gateway manager B2, the application node manager B1_2, the application node manager B2_2, the application node manager B3_2, the application node manager B4_2, the application instance B1_2, the application instance B2_2, the application instance B3_2, and the application instance B4_2 in the second service system 800 is the same as the connection architecture of the application gateway manager B1, the application node manager B1_1, the application node manager B2_1, the application node manager B3_1, the application node manager B4_1, the application instance B1_1, the application instance B2_1, the application instance B3_1, and the application instance B4_1 in the second subsystem.
The application example B1_1 and the application example B2_1 are different application examples on the same machine, the application example B1_1 and the application example B1_2 are the same application example on different machines, and other application examples are similar. In practical applications, taking application instance B1_1 as an example, when application instance B1_1 hangs down or application node manager B1_1 connected to application instance B1_1 hangs down, the embodiment of the present invention may continue to provide services by application instance B1_2 or by application node manager B1_2, thereby ensuring the robustness of the system and improving the processing capability of the system.
Still further, the communication system may further comprise: and the shared MQ manager is respectively connected with the application gateway manager in the first service system and the application gateway manager in the second service system. The number of the shared MQ managers respectively connected with the application gateway manager in the second subsystem and the application gateway manager in the first subsystem is more than 1;
the number of the shared MQ managers respectively connected with the application gateway manager in the first service system and the application gateway manager in the second service system is more than 1.
In the embodiment of the invention, the shared MQ manager is backed up at the same time.
The embodiment of the application adds a service (i.e. a service system) to each application instance, namely adds a corresponding application node manager, an application gateway manager and a shared MQ manager, and adds a backup to all the shared MQ managers at the same time, so that the robustness of the application system is greatly enhanced, and the processing capacity is increased with the increase of the service system.
In the first to fourth embodiments of the present application:
the application establishes an MQ manager (namely the application node manager 300) for each application instance in the subsystem of the application system, and can solve the problem that the application instances mutually occupy resources. The method and the system establish different subsystems for different services with large variety differences in an application system so as to solve the problem that resources are mutually crowded among different services.
According to the application, all application node managers 300 in each subsystem in an application system are connected through an MQ manager (an application gateway manager 500, also called cluster storage) with a special function to form an MQ cluster, topic is defined in the MQ manager with the special function, different application instances of the subsystems realize mutual communication through transceiving topic in the MQ cluster, and the problem of mutual communication among different application instances in the subsystems can be solved.
According to the application, an MQ manager is added to an MQ cluster of a subsystem in an application system to serve as an external gateway manager 400 of the cluster, all interaction with an external system 100 is processed through the external gateway manager 400, and the problem of uniformity of external interaction of different application instances in the subsystem can be solved.
The MQ clusters of different subsystems in the application system are connected through the shared MQ manager 600, and the communication among the subsystems is realized by forwarding topic through the shared MQ manager 600, so that the problem of mutual communication among the different subsystems can be solved.
The application adds a service to each application instance, adds a corresponding application node manager, an application gateway manager and a shared MQ manager at the same time, and adds a backup to all the shared MQ managers so as to enhance the robustness of the application system and the processing capacity of the application system.
It should be noted that, in the present specification, the embodiments are all described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments may be referred to each other.
It is further noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The communication system of the multi-instance multi-subsystem application based on the message middleware provided by the present application is described in detail above, and a specific example is applied in the present application to explain the principle and the implementation of the present application, and the description of the above embodiment is only used to help understanding the method of the present application and the core idea thereof; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (7)
1. A communication system of multi-instance multi-subsystem application based on message middleware comprises a first subsystem, wherein the first subsystem comprises an external system and a plurality of application instances, and is characterized in that the first subsystem further comprises a plurality of application node managers, the number of the application node managers is more than 1, and the application node managers are independent from each other;
the number of the application node managers is equal to that of the application examples, and the application node managers are connected with the application examples in a one-to-one correspondence mode, so that the application examples cannot be influenced mutually, and a single application node manager cannot influence all the application examples;
the plurality of application node managers are respectively connected with the external system.
2. The communication system of claim 1, wherein the first subsystem further comprises: an external gateway manager and an application gateway manager; wherein,
the external gateway manager is connected with the external system;
the application gateway manager is connected with the external gateway manager, and the application gateway manager is respectively connected with each application node manager.
3. The communication system of claim 2, further comprising a shared MQ manager and a second subsystem; wherein,
the architecture of the second subsystem is the same as that of the first subsystem, and an application gateway manager in the second subsystem and an application gateway manager in the first subsystem are respectively connected with the shared MQ manager;
the shared MQ manager is used for realizing topic switching among subsystems.
4. A communication system according to claim 2 or 3, wherein the first subsystem further comprises: a first service system;
the first service system comprises an application gateway manager, an application node manager and an application instance, and the architecture of the first service system is the same as the connection architecture of the original application gateway manager, the original application node manager and the original application instance in the first subsystem.
5. The communication system of claim 3, wherein the second subsystem further comprises: a second service system;
the second service system comprises an application gateway manager, an application node manager and an application instance, and the architecture of the second service system is the same as the connection architecture of the original application gateway manager, the original application node manager and the original application instance in the second subsystem.
6. The communication system according to claim 5, wherein the communication system further comprises: and the shared MQ manager is respectively connected with the application gateway manager in the first service system and the application gateway manager in the second service system.
7. The communication system of claim 6,
the number of the shared MQ managers respectively connected with the application gateway manager in the second subsystem and the application gateway manager in the first subsystem is more than 1;
the number of the shared MQ managers respectively connected with the application gateway manager in the first service system and the application gateway manager in the second service system is more than 1.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811229698.9A CN109257435B (en) | 2018-10-22 | 2018-10-22 | Communication system of multi-instance multi-subsystem application based on message middleware |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811229698.9A CN109257435B (en) | 2018-10-22 | 2018-10-22 | Communication system of multi-instance multi-subsystem application based on message middleware |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109257435A CN109257435A (en) | 2019-01-22 |
| CN109257435B true CN109257435B (en) | 2021-03-23 |
Family
ID=65046635
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811229698.9A Active CN109257435B (en) | 2018-10-22 | 2018-10-22 | Communication system of multi-instance multi-subsystem application based on message middleware |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109257435B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112291254B (en) * | 2020-11-05 | 2023-05-05 | 中国人民银行清算总中心 | Message processing method and device for reliable transaction |
| CN117271152B (en) * | 2023-09-04 | 2024-07-26 | 中电金信软件有限公司 | Registration and query method for application instance information |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101458808A (en) * | 2008-12-31 | 2009-06-17 | 中国建设银行股份有限公司 | Bank management system, server cluster and correlation method |
| CN101980152A (en) * | 2010-10-18 | 2011-02-23 | 华南理工大学 | A mobile middleware system and its implementation method |
| CN103125097A (en) * | 2010-09-17 | 2013-05-29 | 甲骨文国际公司 | Perform partial subnet initialization in middleware machine context |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108476216B (en) * | 2016-03-31 | 2021-01-22 | 甲骨文国际公司 | System and method for integrating a transactional middleware platform with a centralized access manager for single sign-on in an enterprise-class computing environment |
-
2018
- 2018-10-22 CN CN201811229698.9A patent/CN109257435B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101458808A (en) * | 2008-12-31 | 2009-06-17 | 中国建设银行股份有限公司 | Bank management system, server cluster and correlation method |
| CN103125097A (en) * | 2010-09-17 | 2013-05-29 | 甲骨文国际公司 | Perform partial subnet initialization in middleware machine context |
| CN101980152A (en) * | 2010-10-18 | 2011-02-23 | 华南理工大学 | A mobile middleware system and its implementation method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109257435A (en) | 2019-01-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10367852B2 (en) | Multiplexed demand signaled distributed messaging | |
| US9021065B2 (en) | Automated topology formation in dynamic distributed environments | |
| CN101969391B (en) | Cloud platform supporting fusion network service and operating method thereof | |
| US7844851B2 (en) | System and method for protecting against failure through geo-redundancy in a SIP server | |
| US9246780B2 (en) | System and method for supporting port multiplexing in a server environment | |
| WO2017181876A1 (en) | Device state and resource information monitoring method, related device, and system | |
| CN108063813B (en) | Method and system for parallelizing password service network in cluster environment | |
| US20140280988A1 (en) | System and method for parallel multiplexing between servers in a cluster | |
| CN109873736A (en) | A kind of micro services monitoring method and system | |
| EP2838243B1 (en) | Capability aggregation and exposure method and system | |
| US9846618B2 (en) | System and method for supporting flow control in a distributed data grid | |
| CN115567251A (en) | Multi-service isolation method and system for microservice cluster | |
| IES20010064A2 (en) | Computer network system | |
| CN105681426A (en) | Heterogeneous system | |
| CN113468221A (en) | System integration method based on kafka message data bus | |
| CN109257435B (en) | Communication system of multi-instance multi-subsystem application based on message middleware | |
| WO2014173366A2 (en) | Method, device and system for carrying out telecommunication capability group sending | |
| CN100484014C (en) | Distributed cluster service management system and service management method in intelligent network | |
| KR20130130295A (en) | System and method for assigining server to terminal and efficiently delivering messages to the terminal | |
| CN112835717B (en) | Integrated application processing method and device for clusters | |
| CN110519397B (en) | A load balancing system and method for NGINX-based SIP terminal access | |
| CN107357663A (en) | The method and explorer of resource-sharing | |
| CN114598662A (en) | Message queue cluster federal management system and method | |
| CN116980526A (en) | Method, device and equipment for realizing multi-channel queuing machine applied to converged communication | |
| CN111294383A (en) | Internet of things service management system |
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 |