Home › Key concepts › Retries, timeouts and backoff

Key concept · Walk (intermediate) · the same on every platform

Retries, timeouts and backoff

Assume calls fail sometimes, and handle it calmly.

What it is

Networks and services fail briefly. A timeout stops waiting after a set time. A retry tries again. Backoff waits longer between each retry (1 s, 2 s, 4 s) so a struggling service can recover.

See it happen: Problem Lab: a conflict, a back-off and a retry (simulation), recorded from a real run.

Why it matters

Without these, one slow service makes everything slow; with careless retries, you overload it further.

An example

A payment API times out after 5 s; the client retries twice with backoff, using the same idempotency key.

The common mistake

Retrying instantly forever, turning a small outage into a big one.

Where you meet it on each platform

The idea stays the same; only the product name changes.

JobAWSAzureGoogle CloudDatabricksOpen source
Queues and eventshand work to another part safely, even when it is downSQS / EventBridgeService Bus / Event GridPub/SubJobs triggersRabbitMQ or Redis

Related ideas

Where it shows up

Part of the Walk level on these paths: AI Engineering (engineering basics) · Software Engineering (building services).