topic / api-design
API Design
The contract between your service and the world.
REST, GraphQL, gRPC, webhooks, and the contracts that outlive your code. Versioning, idempotency, error formats, and why a good API is designed against its consumers.
4 articles · 0 videos · 0 traces · 0 interviews · 4 total
Articles
gRPC Streaming and Backpressure: HTTP/2 Flow Control and Deadlines Explained
gRPC streaming and backpressure explained: HTTP/2 flow control, stream types, channel capacity, and why client deadlines are the only real backpressure.
GraphQL Field Cost and Overfetching: What Resolution Actually Costs
GraphQL field resolution cost explained: N+1 queries, depth limits, batching, and why overfetching has a price at scale — with realistic resolver code.
REST Resource Modeling: Resources vs Actions, Nesting, and Status Code Semantics
REST API resource modeling explained: resources vs actions, nested resources, and HTTP status code semantics that clients actually depend on.
Designing APIs That Age Well: Compatibility, Additive Changes, and Deprecation
How to design REST APIs that age well: additive changes, removal breakage, compatibility windows, and why deprecation is a migration project, not a release note.
Videos
// empty
No videos yet
Video coverage for this topic is planned. Watch the library page for updates.
Browse videosTraces
// empty
No traces in this topic yet
Traces are the step-by-step walkthroughs. They land as the topic matures.
Browse tracesInterviews
// empty
No interview answers yet
The question-and-answer walkthroughs for this topic are being prepared.
Browse interviewsExplore adjacent
Depth, delivered weekly
One technical dispatch a week on api design and the systems around it.
One technical dispatch per week. No noise.