The Message Hub distributes messages between microservices or the censhare Server. Any microservice can create a topic on the message hub, publish messages to a topic, or subscribe to a topic on the message hub.
Here are some specific use cases:
- Asset update events and asset events: The Sync Service publishes asset update events and asset events to the Message Hub. Other microservices can react on that to synchronize with the censhare Server.
- Permission update events: The Permission microservice listens to changes of permission master data at the censhare Server such as changes in roles. With this information, it updates its local cache.
- Master data update events: The Master Data Service listens to changes of the master data at the censhare Server. It uses this information to update its local cache.
- Success of asset operations: The Asset Management works asynchronous. If a microservice requests an operation, it will not immediately receive an information about success or failure. The Asset Management posts messages about success/failure of an operation to the Message Hub. Other microservices can subscribe to the respective topic to be informed about the result of the requested operation.
- Business Logic Functions can be triggered by messages in a topic of the Message Hub. For example, a business logic function reacts on a Create asset event from the censhare Server. Business Logic Functions can also post messages to trigger other Business Logic Functions or microservices.
- Business Flows: Nodes in a Business Flow can trigger nodes in other Business Flows or trigger Business Logic Functions via publishing of messages to the Message Hub.
- File Microservice: When a file is uploaded into a Hot Folder, the File Microservice publishes a message with file URL to the Message Hub. Other microservices, Business Flows, or Business Logic Functions can react on that message. For example, create an asset from the uploaded file.