Evolving your APIs, a step-by-step approach
summary
Shows how to evolve an HTTP API without breaking users by wiring an Apache APISIX gateway via Docker Compose, creating routes and upstream objects, and attaching plugins for Prometheus, proxy rewrites and rate limiting. Demonstrates mirroring production traffic (proxy-mirror) to validate V2, running a 50/50 canary with the traffic-split plugin, and signaling clients with an RFC-style Deprecation header and sunset link; demos run and expose issues to fix.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:27Apache APISIX, an API Gateway the Apache way
- 0:53Your first API
- 1:43We need to deploy v2!
- 2:20The initial situation
- 3:20An API Gateway can help!
- 4:39Introduce an API Gateway
- 12:24Introduce a versioned resource
- 17:26Move the unversioned resource permanently
- 20:35Make users register
- 25:17Test in production but be smart about it
- 30:37Use proven deployment methods
- 32:03Deprecate your endpoints
- 34:39and afterwards - Time for v3!
related talks
49mEvolving your APIs, a step by step approach
41mEvolving your APIs, a Step by Step Approach
44mEvolving Your APIs, A Step-By-Step Approach
30mEvolving your APIs, a step-by-step approach
38mEvolving your APIs, a Pragmatic Approach
46mEvolving Your HTTP APIs: A Multi-Step Approach
42mEvolving Your HTTP APIs, a Step-by-Step Approach
35mAPISIX, an API Gateway the Apache way
