Reverse Proxy vs API Gateway vs Load Balancer
Three edge layers, three different jobs: one shapes HTTP traffic, one spreads load, one enforces API policy. Here’s where each belongs.
Tiny explainers grouped by topic. Spend less time Googling, more time building.
Three edge layers, three different jobs: one shapes HTTP traffic, one spreads load, one enforces API policy. Here’s where each belongs.
What actually breaks in CORS, which headers matter, and the server configs that fix browser errors without accidentally opening your API.
Practical patterns for rock‑solid APIs: spec styleguide, reusable components, Problem Details errors, auth & versioning, pagination, idempotency, testing, and CI gates. Includes a copy‑paste 3.1 template.
Fixed/sliding windows, token & leaky buckets, GCRA, and real-world implementations (Redis, NGINX, Envoy). Covers headers, bursts, backoff, multi‑DC, and tuning.
Developer token + OAuth, account hierarchy (manager vs customer), GAQL for reporting, safe mutations with validate_only/partial_failure, quotas, and offline conversions.
What counts as a breaking change, URL vs header versions, deprecation signals, and how to evolve APIs without breaking clients. With routing and policy snippets you can paste today.
Which status codes to use, how to shape errors consistently, and what to log so clients get clear signals and you get useful telemetry.
A diagram-first walkthrough of OAuth 2’s Authorization Code + PKCE flow: who does what, how the redirects work, and where the tokens end up.
Where a gateway earns its keep, where a reverse proxy is enough, and why pushing business logic to the edge usually backfires.
A quick, practical guide to choosing between REST, GraphQL, and gRPC for new and existing services.