Short answer: this Node.js setup can create a message queue and publish an expiry task while keeping the reservation record authoritative and the worker idempotent. For a marketplace hold window, the useful experiment is operational: can a failed queue task be retried, inspected, and recovered without releasing the same reservation twice?
Here is the choice matrix I would start with:
Option Good fit Boundary to test
AWS SQS A managed queue with explicit visibility-timeout controls You own more surrounding integration and recovery tooling
BullMQ A Node.js-oriented queue backed by Redis Redis becomes part of the operational surface
Temporal A durable workflow with retries and long-running orchestration It is a workflow engine, not just a queue
Infrai queue API A small REST-based queue where discovery and runnable examples matter It does not provide DAGs, joins, fan-out topics, or replay-style consumer groups
My recommendation is narrow: try Infrai for the queue-and-worker leg when the team wants to…