Optimized publishing / signing of a cluster of JMS browsers and conflicting messages in StackOverFlow for response

I want to create a publishing / subscribed distributed message publishing structure that can manage huge amounts of message traffic with some information at the broker level. I don't know if there is a topology that describes this, but this is the model that I will do:

EXAMPLE MODEL A

A) There are two working message brokers (ideally, everything is on the local host, if possible, for a simpler demonstration):

  • Broker-a
  • Broker-b

B) Each broker will have 2 listeners and 1 publisher.

Example Figure

[subscriber A1, subscriber A2, publisher A1] ↔ BrokerA ↔ BrokerB ↔ [publisher B1, subscriber B1, subscriber B2]

  • -X A, Broker-B ( ), -X Broker-B.

  • ELSE, A B, B // , , .

?

, " " - , . , , :

  • ...

... .

?

: - JMS, ?

stackoverflow : JMS Cluster. , , , :

.

,

Gene

+3
2

WebSphere MQ , :

  • WebSphere MQ;
  • , , .

, , QMgrs, . , . , , , . QMgr , - WebSphere Message Broker. ( WebSphere WMQ , WMB , ..)

0

Source: https://habr.com/ru/post/1744838/


All Articles