mufassall

Foundations / 3 / 3

Napkin math

Before building a courier-tracking service, size it on a napkin: users to requests per second, requests to bytes per day, bytes to disks, bandwidth and servers. Rough numbers, a few minutes, and the expensive mistakes show up before the first line of code.

  • 12 min
  • Beginner
  • 10 steps
Peak requests
2 000 /s
Database size
—
API egress per second
—
App servers
—
Open in Lab
  • request
  • reply
  • redelivery
  • duplicate
  • lost

Numbers are a model scenario, not measurements

The real request

Courier app → Tracking API

Request

POST /v1/pings HTTP/1.1
Host: api.example.com
Authorization1: hidden

{
  "courier_id": 2"c_1207",
  "lat": 341.3111,
  "lon": 69.2797,
  "ts": 41795392843
}

Response

HTTP/1.1 204 No Content
  1. Authorization · hidden — Each courier's token. A secret, so it is hidden here.
  2. courier_id — Who sent it. Pings are looked up by courier, so this will be the first column of the index.
  3. lat — Latitude, together with lon the position. Two numbers, 16 bytes.
  4. ts — When the phone took the reading, not when the server got it. Phones can be offline and send late.
Course: 42 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. CDN and edge caching
  3. 03 Data & storage

    1. SQL and NoSQL
    2. Database indexes
    3. Storage engines: B-tree and LSM
    4. Database replication
    5. Sharding
    6. Consistent hashing
    7. Unique IDs
    8. CAP: when the link breaks
    9. Consensus and leader election
    10. Transactions
    11. File uploads
  4. 04 Communication

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

    1. Redundancy and failover
    2. Rate limiting
    3. Timeouts and retries
    4. Observability
  6. 06 Architecture

    1. Microservices
    2. Service discovery
    3. Sagas and the outbox
    4. Batch vs stream
  7. 07 Security

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

    1. Testing
    2. CI/CD: from commit to production
  9. 09 Whole systems

    1. From requirements to design
    2. Design a URL shortener
    3. Design a news feed
    4. Design a chat
  10. 10 Business processes

    1. Payment gateway