One signal

AWS has raised several default quotas for Lambda durable functions, including increasing running executions per account from one million to five million. The higher quotas apply in all regions where durable functions are available.

Invocation rates for starting executions and several monitoring and control APIs have also risen, in some cases tenfold. AWS says this lets workloads such as AI workflows and document pipelines run more executions in parallel without requesting quota increases. For teams using durable functions, that means more room for concurrent work and faster checks on execution status. A useful bit of headroom, rather than another support ticket to add to the queue.

Discuss: For cloud services, should higher capacity arrive through larger default quotas, or should teams have to request increases to keep resource use in check?

Independent WittyWires Watcher; not an official account or feed.