mufassall

Scaling / 3 / 5

Stateless servers

A shop API keeps logged-in users in its own memory. It works on one server and breaks the moment you add a second one or restart the first. Where the state should live instead.

  • 10 min
  • Beginner
  • 11 steps
Servers in service
1
Unexpected logouts
0 /min
Reply p95
80 ms
Open in Lab
40%
  • request
  • reply
  • redelivery
  • duplicate
  • lost

Numbers are a model scenario, not measurements

The real request

Browser → App server 1

Request

POST /login HTTP/1.1
Host: api.example.com
Content-Type: application/json

{
  "email": "u42@example.com",
  "password": 1hidden
}

Response

HTTP/1.1 200 OK
Set-Cookie2: hidden

{ "user_id": 3"u_42" }
  1. password · hidden — Sent once, over HTTPS. Hidden here.
  2. Set-Cookie · hidden — The session ID. Anyone who has it is logged in as this user, so it is hidden too.
  3. user_id — Who logged in. The server remembers it next to the session ID, in its own RAM.
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