REST Topic

REST

An API contract is forever. These posts cover webhook reliability, rate limiting beyond the textbook, HTTP caching headers, and the design choices that make an API survive contact with real callers.

Backend

Posted on Jun 4, 2026

Your Internal APIs Shouldn't Be REST

REST is a choice you make for outsiders. Between your own services an untyped text protocol is a liability: payload bloat, no schema, breakage at runtime.

REST vs GraphQL Is Over. You're Now Running Both, Badly.

REST vs GraphQL got declared a tie: use both. Nobody costs that out. Two contracts, the HTTP caching you lost, a leaky BFF, and the N+1 that just moved.

The Endpoint That Always Returns 200

REST APIs that wrap every error in HTTP 200 break retries, caches, load balancers, circuit breakers, and observability. The status code is part of the contract.