Middleware concept for asynchronous, decoupled communication between distributed systems using messages, brokers, queues and topics.
Message-Oriented Middleware (MOM) is an architectural concept for decoupled communication between distributed applications via asynchronous messaging channels. It provides reliability, scalability and configurable QoS through brokers, queues and topics. Implementations differ in persistence, routing and transactional support.
Number of processed messages per second as a measure of capacity.
Time from sending a message to processing by the consumer.
Share of messages landing in dead-letter queues as an indicator of errors.
RabbitMQ as broker to decouple order intake, payment and delivery services in a microservice architecture.
Apache ActiveMQ is used to connect JMS-based legacy systems to modern event processing pipelines.
Lightweight broker architecture using MQTT for mobile and embedded devices to transmit telemetry.
Analyze requirements: reliability, throughput, ordering.
Define message formats and schemas and set a versioning strategy.
Select appropriate broker software, configure and operate it in a cluster.
Implement consumers/producers, run tests for failure and load scenarios.
Establish monitoring, alerting and recovery processes.