YOUnite uses Active MQ (YOUnite uses ActiveMQ (AMQ, https://activemq.apache.org ) as its message broker for communication between the YOUnite MDM API service, adaptors and the user interfaceadaptors (Adaptors).
| View file | ||||
|---|---|---|---|---|
|
AWS services:
AWS services like SNS (Simple Notification Service) and SQS (Simple Queue Service) could be used together to accomplish the notification based messaging system, but to not get tied to a single vendor, we are using the standard based messaging service, that is JMS (Java Message Service). The intent is to stick to the JMS API specifications and not use implementation/vendor specific features and extensions, thus leaving the window open to switch brokers if the need be.
Recipes for Configuring Artemis
YOUnite has a Docker compose image that is pre-configured to work with YOUnite. However, follow these recipes if you want to configure your own Artemus system or image:
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
Configuring Message Broker for YOUnite
Communicating with Message Bus from YOUnite API
Configuring Artemis to Run in a YOUnite Adaptor
Communicating with Message Bus from YOUnite UI
Message broker configuration for YOUnite Adaptor