Tune workers, retries, and dead-letter behavior while jobs move through an async queue with failures and poison messages.
Interactive scenario
Use the controls below. Feedback appears immediately and final scores stay in this browser.
Concept notes
Message Queue Simulator is focused practice for Async jobs, retries, visibility timeout, and dead-letter queues. It explains why each answer is safe, risky, or production-ready.
Message queues make backends more resilient, but they introduce new choices around concurrency, retries, and failed jobs. This simulator lets you explore those choices safely.
Queues decouple producers from consumers. They smooth bursts, allow retries, and keep slow work out of synchronous request paths.
This simulator models queue capacity and at-least-once delivery attempts. Broker delivery is not the same as exactly-once business processing: consumer deduplication and transactional side-effect boundaries are practiced separately in Idempotent Consumer Lab.
Retries improve reliability, but jobs must be idempotent because a retried job may run more than once. Dead-letter queues isolate messages that repeatedly fail.
Use the main site for deeper reading after playing.
Use tools from the main site when you want to inspect real inputs.
Short answers for how this game fits backend interview and study practice.
It is the period when a claimed message is hidden from other consumers. If processing fails or times out, the message can become visible again for retry.
High retry counts can hide bugs, waste capacity, and keep poison messages cycling instead of being inspected.
Top 10 scores for the current ruleset. No account required.
Loading leaderboard...
Finish the game to load your latest local score.