What it is
A task queue hands a task to one worker for a limited time: a lease, or in Amazon SQS the visibility timeout. If the worker finishes and acknowledges in time the task is done; if the lease runs out first the task is handed to someone else. This simulator runs workers, heartbeats, crashes and freezes against that rule and shows duplicates, zombie work and recovery time.
When to use it
Use it to choose a lease length and heartbeat interval, to see why a crashed worker’s task only comes back after the lease, why a frozen worker can still write after it lost the task, what fencing tokens and idempotent sinks fix, and how retries, delays and dead-letter queues bound poison tasks.
Gotchas & limits
A teaching model of the documented SQS visibility-timeout and dead-letter behaviour (Amazon SQS developer guide, checked 2026-10-22); real services differ in details. Durations, polling and delays are parameters, not measurements, and no throughput or cost is shown. The sweep is a Monte-Carlo estimate with a confidence interval, not a guarantee.