...
The functionality that the YOUnite Router (i.e requires from the Message Broker is relatively straightforward and is typical of most Message Bus systems.
Note: "Router" - the component of the YOUnite API Service that manages master data transfer between adaptors
...
.
From the Router’s standpoint, the Message Bus is the way the Router communicates with the Adaptors. YOUnite creates will be one queue set up adaptor for incoming messages from the Router. This This queue will be used for state and data messages. There There will also be a queue for data and a queue for state that each adaptor can put messages on to be received by the Router.
...
Since an adaptor may be paused, data messages can queue up indefinitely. HenceHence, it will be highly desirable to be able to get information on the data queue Data Queue for a paused adaptor so a zone admin Zone Admin can see how many data messages have been queued up and are awaiting await processing.
So, to To summarize the Router:
Connects to the Message Broker and reestablished reestablishes connections (i.e. resume resumes queue listeners) to durable but , dynamically-defined queues.
Creates data queues for each adaptor upon creation
Destroys data queues upon adaptor deletion
Can readMessage off a queue
Can postMessages to a queue
Can postMessage to a topic
Can temporarily halt delivery of certain types of messages
Can resume delivery of certain types of messages
Can inspect a queue (get overall stats--, such as messages in wait, longest wait in queue, etc.)
...