Message Broker Service
YOUnite uses ActiveMQ (AMQ, https://activemq.apache.org ) as its message broker for communication between the YOUnite MDM API service, and the adaptors (Adaptors).
The adaptors, Message Broker (bus), and the router portion of the YOUnite Data Hub make up the "Adaptor Layer" of the YOUnite MDM runtime stack with a primary task to synchronize source entities throughout the entire YOUnite ecosystem.
Background
Recipes for Configuring the Message Broker
Comments
Also, I think "message broker," "broker," and "AMQ" are being used throughout these sub pages to mean the same thing. Is there a preferred way, out of those three, to refer to it? If so, can/will it make sense to use that one term throughout? My vote would be for "message broker" l.c., as it seems the most descriptive.
Anuj and I agreed that broker is the generic, general term but sometimes (infrequently) we'll need to refer to the message bus. When we are talking implementation specific things like how to configure the broker, we'll need to refer to AMQ.
Perhaps you can give us some guidance on that and feel free to edit as you see fit. Perhaps make a cleaner intro.
Mark, I know it is probably obvious to you, but would it be helpful to briefly mention a couple of examples of instances when one might want to modify the Docker Compose image or configure their own AMQ system or image?