Evolving your APIs, a Step by Step Approach
summary
Step‑by‑step recipe to evolve an HTTP API without breaking users: deploy Apache APISIX behind nginx via Docker compose, add routes and an upstream, expose metrics to Prometheus and Grafana, issue 301 redirects for legacy endpoints, create a consumer + API key for rate tiers, write a small Lua plugin to enforce registration limits, mirror traffic to a V2 after rewriting prefixes, run a 50% canary, compare error curves, then publish RFC deprecation and Sunset headers; all demos run and demonstrate the flow.
AI-written summary · about
chapters (9)
- 0:00Introduction to API evolution
- 13:20Setting up API Gateway demo
- 18:25Versioning APIs with API Gateway
- 22:43Redirecting old API routes
- 25:36API consumer authentication
- 29:33Testing new API versions
- 31:29Canary release with API Gateway
- 36:58Deprecating old API versions
- 39:46Summary and next steps
related talks
30mEvolving your APIs, a step-by-step approach
35mEvolving your APIs, a step-by-step approach
49mEvolving your APIs, a step by step approach
44mEvolving Your APIs, A Step-By-Step Approach
46mEvolving Your HTTP APIs: A Multi-Step Approach
42mEvolving Your HTTP APIs, a Step-by-Step Approach
38mEvolving your APIs, a Pragmatic Approach
26mEvolving Your API