mufassall

Reliability / 6 / 6

Backpressure

A mobile app sends analytics events to an ingest API, which keeps them in memory until a writer stores them. When the database slows down, events arrive faster than they leave, the buffer has no limit, and the API dies of memory with 1.8 million events already confirmed. Backpressure is how a system says "slower" back up the chain: a bounded buffer, a chosen way to overflow, 429 with Retry-After, consumers that pull, shedding by priority and a limit at the door.

  • 14 min
  • Intermediate
  • 10 steps
API memory
40 MB
Event delay
0.5 s
Events lost
0
Events turned away
0 %
Open in Lab

40%60%
  • request
  • reply
  • redelivery
  • duplicate
  • lost

Numbers are a model scenario, not measurements

The real request

Mobile apps → Ingest API

Request

POST /v1/events HTTP/1.12
Host: ingest.example.com
Authorization: hidden

{
  "device": 1"d_7f",
  "events": [
    { "type": "screen_view", "ts": 1763481600 },
    { "type": "add_to_cart", "ts": 1763481602 }
  ]
}

Response

HTTP/1.1 202 Accepted3
{ "accepted": 450 }
  1. device — Which phone sent the batch.
  2. events — Up to 50 events per request, so the app does not open a connection per tap.
  3. 202 Accepted — "Taken", not "stored". The event lives only in the API's memory so far.
  4. accepted — How many events of the batch the API took.

What happens if…?

Put in your own numbers: the result and the formula update at once.

Events per second arriving at the API.

Writers storing events in parallel.

How long one writer needs to store one event. 5 ms while the DB is slow.

Result

Load ρ
0.60
Chance to wait
29%
Average wait in the buffer
0.4ms
Total delay
2.4ms
Average events in the buffer
0.4

Working

μ = 1000 / 2 ms = 500.0/s
ρ = λ / (c × μ) = 1 200 / (4 × 500.0) = 0.60
P(wait) = ErlangC(c = 4, λ/μ = 2.40) = 0.287
Wq = P(wait) / (c × μ − λ) = 0.287 / 800.0 = 0.4 ms

A simplified teaching model: it shows direction and scale, not a benchmark.

Build it yourselfCheat sheetCompare lessons

Course: 74 lessons
  1. 01 Foundations

    1. The life of a request
    2. Latency and throughput
    3. Napkin math
  2. 02 Scaling

    1. Scaling up vs scaling out
    2. Load balancing
    3. Stateless servers
    4. Caching
    5. Cache invalidation
    6. CDN and edge caching
  3. 03 Data & storage

    1. SQL and NoSQL
    2. Database indexes
    3. Geo search: who is nearby
    4. Full-text search
    5. Vector search
    6. Storage engines: B-tree and LSM
    7. Bloom filters
    8. Database replication
    9. Sharding
    10. Consistent hashing
    11. Unique IDs
    12. CAP: when the link breaks
    13. Consensus and leader election
    14. Transactions
    15. File uploads
  4. 04 Communication

    1. API styles
    2. Message queues
    3. Pub/sub and event logs
    4. Real-time updates
    5. Reliable callbacks
    6. Sending webhooks reliably
  5. 05 Reliability

    1. Redundancy and failover
    2. Rate limiting
    3. Timeouts and retries
    4. Observability
    5. SLOs and error budgets
    6. Backpressure
  6. 06 Architecture

    1. Microservices
    2. Service discovery
    3. Sagas and the outbox
    4. Change data capture (CDC)
    5. Transactional outbox
    6. Distributed locks
    7. Batch vs stream
    8. Multi-tenancy
    9. Event sourcing
  7. 07 Security

    1. Authentication
    2. Authorization
    3. Encryption and secrets
    4. Secrets management
  8. 08 Shipping

    1. Testing
    2. CI/CD: from commit to production
    3. Zero-downtime migrations
    4. Feature flags
  9. 09 Whole systems

    1. From requirements to design
    2. Design a URL shortener
    3. Design a news feed
    4. Design a chat
    5. Design a video streaming site
    6. Design search autocomplete
    7. Design a job scheduler
  10. 10 Business processes

    1. Payment gateway
    2. Money and rounding
    3. Double-entry ledger
    4. Payment reconciliation
    5. Subscription billing
    6. Electronic digital signature
    7. Document lifecycle
    8. Audit log
    9. Notification delivery
    10. Bulk import
    11. Refunds and chargebacks
    12. Gapless document numbering
  11. 11 Case studies

    1. Case: how Discord stores messages
    2. Case: Figma multiplayer editing