Last Minute Notes
  • Github
  • Docs
  • Learn
    @sayanstwt
Lessons
0/37 done
  • DNS Resolution
  • Content Delivery Networks
  • Load Balancing
  • Gateways, Proxies & Meshes
  • Caching
  • Rate Limiting
Learn/System Design/Traffic & Edge

Gateways, Proxies & Meshes

6 min Intermediate 7 steps

Where auth, routing and retries live between clients and services.

Services
3
Auth copies
3
Clients know
3 addresses
OrdersauthlimitslogsWeb appUsersauthlimitslogsMobile appPaymentsauthlimitslogsthe same cross-cutting code, copied into every service
request response data
In this lessonStep 1 of 7
  1. The problem
  2. Proxy
  3. Gateway
  4. BFF
  5. Mesh
  6. Guidance
  7. Recap
Step 1 / 7problem

Every service does the edge work

Clients call each service directly. Every service has to check auth, apply rate limits and log requests on its own.

Clients must also know every service address.

Key idea

Cross-cutting concerns copied into every service drift apart. Put them in one place.

←→ step·R replay·Space pause

You'll learn

  • Why cross-cutting concerns belong at the edge
  • Tell a reverse proxy from an API gateway
  • Use a BFF to shape responses per client
  • Know what a service mesh adds, and when to skip it
Read the full notesHLD Building Blocks, 5