More queues per account - up to 10,000
Developers building on Queues can now create up to 10,000 queues per account, enabling easier per-user, per-job and sharding use-cases.
Higher consumer concurrency limits
This limit will continue to grow during the Queues beta.
Consumer concurrency (enabled)Queue consumers will now based on the number of messages being written to the queue. To control or limit concurrency, you can explicitly define a for your consumer.
Consumer concurrency (upcoming)
Queue consumers will soon automatically scale up concurrently as a queues’ backlog grows in order to keep overall message processing latency down. Concurrency will be enabled on all existing queues by 2023-03-28.
To opt-in, you do not need to take any action: your consumer will begin to scale out as needed to keep up with your message backlog. It will scale back down as the backlog shrinks, and/or if a consumer starts to generate a higher rate of errors. To learn more about how consumers scale, refer to the documentation.
Explicit acknowledgement (new feature)
This allows you to mark a message as delivered as you process it within a batch, and avoids the entire batch from being redelivered if your consumer throws an error during batch processing. This can be particularly useful when you are calling external APIs, writing messages to a database, or otherwise performing non-idempotent actions on individual messages within a batch.
Higher per-queue throughputThe per-queue throughput limit has now been .
sendBatchmethod which supports sending up to 100 messages at a time.