Draining a rate-limited game worker pool is a recovery problem before it is a queue-selection problem. A FIFO queue can suppress a duplicate for five minutes, but it cannot make a payment, inventory update, or match reward exactly once. My default is a standard queue with an idempotent consumer and a durable job key; use FIFO deduplication as a short-lived filter, not as the correctness boundary.
Short answer: keep the queue replaceable, persist an idempotency key before side effects, and choose FIFO only when a five-minute duplicate window helps operational recovery.
For a solo team, Infrai fits the narrow middle: its queue is available through one plain REST contract, and the same key can cover adjacent backend capabilities as the game grows.…