Loading content
RabbitMQ is an open-source message broker based on the AMQP protocol. It enables flexible and reliable communication between applications and services. RabbitMQ supports various messaging patterns and offers extensive features for message management.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
RabbitMQ is a widely used message broker that facilitates messaging between applications and services.
RabbitMQ began as an open-source implementation of the Advanced Message Queuing Protocol at Rabbit Technologies and was maintained from 2007 by VMware and later Broadcom.
Producers publish messages to exchanges, which route them through bindings into queues. Consumers acknowledge processing; persistence, prefetch, and dead lettering shape delivery, throughput, and failure handling.
Exchanges determine message routes.
Queues buffer work for consumers.
Acknowledgements mark successful processing.
RabbitMQ decouples services for asynchronous workflows and load spikes. Delivery guarantees, ordering, retries, and monitoring of growing queues must be defined for each business process.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.