A Worker Count Is Not a Throughput Plan

Wed, 01 Jan 2025 00:00:00 +0000

Four Laravel queue workers complete 114 waiting jobs per second where one worker completes 37. Keep the worker count at four, make every job update the same database row, and the rate falls to 32. Make each job fail twice before succeeding, and those four workers perform 540 attempts to produce 180 effects.

Nothing is wrong with the worker setting. It is answering three different workloads.

A worker count describes available executors. It says nothing about whether a job can run in parallel, which dependency must absorb the concurrency, or how many attempts are needed for one business effect. A throughput plan needs those parts too.

A Queued Command Changes the Contract

Sat, 01 Apr 2023 00:00:00 +0000

Send the same payment-capture request through two Laravel routes.

The synchronous route returns 204 after the provider has created charge ch_001 and the order records that reference. When the provider returns 503, the HTTP request returns 500 and the order remains unpaid.

The queued route returns 202 while the order is still unpaid and the provider ledger is empty. Its response contains an operation URL. Cancel the order before a worker starts and that operation later becomes refused; the provider is never called.

Queues on Brian Faust

A Worker Count Is Not a Throughput Plan

A Queued Command Changes the Contract