Configuring the message broker
Martini uses the configured broker when saving and indexing Tracker and invoke monitor documents1, communicating with connected instances, listening to destinations for JMS listener endpoints, and more – like user-written JMS-reliant applications.
Why use a message broker?
Message brokers allow clients to proceed with other processes, whether or not the current service has provided a response.
Multiple brokers can be configured to work as a federated network of brokers for scalability purposes.
The location of the applications don't need to be known which means changes in details about the services can also be made without affecting or disrupting the client.
Sources or destinations don't have to be simultaneously available in order to send or receive messages.
In production environments, it is recommended to replace the embedded ActiveMQ broker with something more robust, especially when Martini actively uses the broker for any of the tasks above.
In the following pages, we'll teach you how to setup the message broker instance and how to make Martini run your selected message broker.
- ActiveMQ as the instance message broker
- ActiveMQ Artemis as the instance message broker
- RabbitMQ as the instance message broker
For performance efficiency. ↩