Building Type-Safe API Clients From OpenAPI Schemas
Stop hand-maintaining API interfaces that drift from the backend — generate them from OpenAPI and turn breaking changes into compile errors.
Tag
7 articles
Stop hand-maintaining API interfaces that drift from the backend — generate them from OpenAPI and turn breaking changes into compile errors.
A practical framework for versioning APIs and deprecating old versions without breaking clients you don't control or can't even see.
How Stripe layers per-request rate limiting with system-wide load shedding to keep its payments API available when traffic spikes or dependencies slow down.
How request batching and the DataLoader pattern eliminate N+1 query storms in APIs, with a look at when batching helps and when it just adds latency.
Wildcard generics confuse most developers on sight, but the PECS rule turns a wall of question marks into a mechanical, memorable decision.
Stripe's approach to API versioning uses per-account pinned versions and request/response transforms instead of forcing every integration onto the latest shape.
Optional was designed for exactly one purpose: expressive return types. Used anywhere else, it tends to add ceremony without removing any risk.