Short answer: For a Node.js queue service that must implement rate-limiting in message processing, use durable delivery with a shared rate budget, an idempotent expiry command, and a retry path that preserves the rental reservation record.
That combination matters more than the queue brand. A rental hold that expires late can block inventory; one that expires twice can create a much harder reconciliation problem.
Keep the command boring.
The worker should claim an expiry job, wait for capacity, verify the hold is still eligible, and commit the state change in one transaction. Keep the queue responsible for delivery. Keep business truth in the property database. That boundary gives an operator somewhere reliable to start recovery when a worker disappears.…