System Design
05Design patternsManaging long-running tasks

05 · Reusable pattern

Managing long-running tasks

Expose progress, cancellation, checkpointing, leases, retries, and result retention.
8 minConcept guideReference-informed · independently authored
01

Lesson spine

What you need to understand.

Long work should outlive the initiating request and expose durable state, progress, cancellation, and recovery.

01

Async task contract

Create a job, return its ID immediately, and expose status or event endpoints instead of holding a request for minutes.

02

Leased ownership

A worker claims the job for a bounded time and heartbeats; expiry allows another attempt after a crash.

03

Checkpointing

Persist resumable stage state often enough to bound wasted work without turning every inner step into storage traffic.

04

Progress

Report durable milestones or processed units, not invented percentages, and include current stage and last update time.

05

Cancellation

Record intent, fence later commits, release capacity, and define which external effects cannot be undone.

06

Retry and dead letters

Classify transient failures, back off with jitter, cap attempts, and surface terminal jobs for operator repair.

02

Before the boxes

Frame the decision.

Outcome

What must work

Expose progress, cancellation, checkpointing, leases, retries, and result retention.

Scale

What changes the design

Runtime · checkpoint cost · retry probability · progress rate · retention

Boundary

What owns the truth

Identify the component that commits authoritative state, then separate synchronous confirmation from derived work.

Non-goal

What stays simple

Do not add global coordination, multi-region writes, or a specialized store until a requirement earns the complexity.

03

Architecture map

Trace ownership, not just traffic.

Managing long-running tasks · concept mechanism

Walk one representative request across every arrow. Say whether the handoff is synchronous or asynchronous, what identity makes a retry safe, and which step changes authoritative state.

  1. 01

    Client — Creates job Define the output contract before moving to the next owner.

  2. 02

    Job store — Owns state Define the output contract before moving to the next owner.

  3. 03

    Queue — Buffers stages Define the output contract before moving to the next owner.

  4. 04

    Worker — Claims lease Define the output contract before moving to the next owner.

  5. 05

    Checkpoint store — Persists progress Define the output contract before moving to the next owner.

  6. 06

    Progress stream — Updates client Define the output contract before moving to the next owner.

  7. 07

    Cleanup — Expires results Confirm the result and emit the evidence needed to reconcile it.

04

Decision table

Make the trade-offs explicit.

DecisionDefensible positionCost to acknowledge
Primary mechanismFine checkpoints reduce retry waste but add writes and resume complexity.The stronger guarantee usually adds coordination, latency, state, or operational work.
Sync vs. asyncKeep only correctness-critical confirmation synchronous. Move derived views, notifications, analytics, and cleanup behind a durable boundary.Async work needs idempotency, lag monitoring, replay, and a product definition for partial completion.
Simple vs. scaledBegin with one logical owner and a clear API. Partition or replicate only the resource proven to be the first bottleneck.Migration requires stable identities, versioned contracts, backfill, and a rollback path.
05

Failure review

Design the recovery path.

DetectBoundRetry safelyReconcileLearn

Topic-specific risk

Duplicate ownership and cancellation during commit create contradictory outcomes.

Response

Persist enough identity and state to distinguish retry, resume, compensation, and operator repair.

Dependency timeout

A timeout is ambiguous: the remote side may have failed, succeeded, or still be running.

Response

Use deadlines, bounded backoff with jitter, idempotency keys, and a status or reconciliation path.

Overload or skew

Average capacity can look healthy while a tenant, key, partition, region, or expensive request saturates one owner.

Response

Expose queue depth and hot-key share, apply backpressure, isolate tenants, and degrade optional work before correctness.

06

Evidence + level bar

Prove the design can be operated.

Core signals

Health of the promise

Measure user-visible latency or freshness, correctness drift, saturation, retry volume, and time to recover. Alert on the failed promise—not only CPU.

Mid-level

Complete and clear

Finish the happy path, identify the state owner, choose reasonable building blocks, and explain one scale mechanism.

Senior

Trade-offs and failure

Separate read and write paths, define consistency, explain partitioning, and make duplicate or partial failure safe.

Staff+

Evolution and operations

Discuss multi-region boundaries, migration, tenant isolation, capacity, observability, and how the architecture changes over time.

07

Interview language

Open the deep dive with a claim.

“For Managing long-running tasks, the decision I want to make explicit is this: Fine checkpoints reduce retry waste but add writes and resume complexity. I’ll trace the state-changing path first, show where the result becomes durable, then test the design against the highest-risk failure and our target scale.”

08 · Retrieval check

Can you defend it without the page?

  1. For Managing long-running tasks, where is the correctness boundary and which failure would you test first?
  2. Which component owns committed truth, and what event or response proves the commit?
  3. Where is the first scaling or coordination bottleneck under the stated envelope?
  4. What happens after an ambiguous timeout or duplicate operation?
  5. Which complexity would you remove at one hundredth of the scale?