03 — API Gateway Patterns
Purpose
[stub: api-gateway-patterns]
See Also
- API Gateway — case study at
system-design/15-complete-case-studies/31-api-gateway/api-gateway.md
Metadata
| Author | Amit Singh |
| Scope | patterns |
Local graph
Linked from 2 notes
02 — Strangler Fig
Incrementally replace a legacy system by routing new functionality to a new implementation while the old system continues to run. Named after the fig tree that grows around and eventually replaces its host.
Patterns
A book-shaped table of contents for reusable engineering patterns spanning object-oriented design, enterprise architecture, distributed systems, messaging, APIs, cloud infrastructure, observability, security, concurrency, AI/agentic systems, and organizational design — grounded in production experience at scale.
Related notes
01 — REST Patterns
Resource modeling, pagination, filtering, HATEOAS, and versioning — the design decisions that separate a well-behaved REST API from an RPC call wearing HTTP verbs.
02 — RPC Patterns
gRPC and Protobuf, and the unary, streaming, and bidirectional-streaming call shapes — when RPC's tighter contract and lower overhead beat REST's looser one.
Patterns
A book-shaped table of contents for reusable engineering patterns spanning object-oriented design, enterprise architecture, distributed systems, messaging, APIs, cloud infrastructure, observability, security, concurrency, AI/agentic systems, and organizational design — grounded in production experience at scale.
02 — Pattern Selection & Trade-offs
How to choose between competing patterns under real forces: naming the context, weighing trade-offs and consequences, composing multiple patterns together, and recognizing when a pattern has outlived its fit.