RabbitMQ, live
One broker with a topic exchange, four queues and a few consumers, all running right here. Take a guided story, or play: add a publisher, crash a consumer, bind a queue with your own pattern, drag the timeline back, or type rabbitmqctl list_queues in the terminal.
Connecting to the broker…
AMQPS
Connect from your computer
AMQPS (port 5671) and the management UI (port 15672) listen on the server’s localhost only. With the SSH tunnel open, log in to AMQPS with your client certificate and no password; the management UI uses the admin password.
bash infra/local/connect.sh setup
bash infra/local/connect.sh tunnel
bash infra/local/connect.sh rabbitmqNOTES
RabbitMQ notes
The concepts behind what you see above. They also live under Notes, tagged #rabbitmq.
- RabbitMQ lab: a second broker on shared partsA RabbitMQ lab at /rabbitmq built like the Kafka one, after first pulling the clock, rewind, story mode and toolbar out of Kafka into shared packages; a real RabbitMQ on the server with certificate login; and guided steps that loop with a draggable bar.
- RabbitMQ: acks, prefetch and redeliveryWhy a queue keeps a message until the consumer acks it, how prefetch decides who gets the next one, and what happens to messages a consumer was holding when it dies.
- RabbitMQ: dead letters, TTL and length limitsWhere a queue sends the messages it gives up on, how message TTL and a dead-letter exchange make a delayed retry, and what a full queue does with one more message.
- RabbitMQ: exchanges, bindings and routingPublishers never write to queues. How the four exchange types decide which queues get a copy, what topic patterns match, and what happens to a message nothing matches.
- RabbitMQ: running one in a container, with certificate loginHow the real broker behind /rabbitmq?mode=real is set up: config in conf.d, users and queues from definitions.json, password hashes made with openssl, EXTERNAL login by certificate name, a memory cap, and ports only on localhost.
- RabbitMQ vs KafkaA queue that forgets acked messages versus a log that keeps everything: how the two differ in routing, delivery, ordering, replay and failure, and when each fits.
- Rewind, replay and loop in a deterministic simulationHow the Kafka and RabbitMQ labs go back in time without snapshots: a fixed-step clock, a log of outside actions, and replay from the start. Then the same trick turned into a looping, scrubbable step player.