mufassall

Communication / 1 / 5

API styles

One screen of a food-delivery app, "My orders", built with REST, then GraphQL, with gRPC between services. Where each style fetches too much or too little, and the habits every API needs: cursor pagination, versioning and idempotency keys.

  • 12 min
  • Beginner
  • 12 steps
Calls per screen
1
Screen load
180 ms
Data per screen
0.1 MB
Double orders
0 /day
Open in Lab
  • request
  • reply
  • redelivery
  • duplicate
  • lost

Numbers are a model scenario, not measurements

The real request

Phone app → REST API

Request

GET /v1/orders?limit=20 HTTP/1.11
Host: api.example.com

Response

HTTP/1.1 200 OK
{
  "data": 2[
    {
      "id": "ord_981",
      "status": "delivered",
      "total": 84000,
      "restaurant_id": 3"r_7",
      "address": { ... },
      "items": 4[ ... ]
    }
  ]
}
  1. GET — Reading only. Safe to repeat and easy to cache.
  2. data — The list itself. Keeping it under a key leaves room for paging info next to it.
  3. restaurant_id — Only an ID. The screen needs the name, which is not here.
  4. items — Bulky fields the screen never shows, sent on every load anyway.
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