Evolving your APIs, a Pragmatic Approach
summary
Demo uses Apache APISIX as an API gateway to front two services (V1: Spring Boot Java, V2: Kotlin), configured via etcd and Docker Compose. Shows creating upstreams and a proxy-rewrite route to strip /v1, adding Prometheus metrics, and a custom Lua plugin that enforces registration with consumer/key-auth (demo rate limit: 2 calls/minute for anonymous). Presents traffic mirroring for validation, a 50/50 canary split, then response-rewrite to add the deprecation header and a sunset URL before retiring V1.
AI-written summary · about
chapters (14)
- 0:00Introduction to API evolution
- 1:27Why API versioning matters
- 2:51Brief history of web servers
- 10:10APIs as integration glue
- 13:21Introducing API Gateway
- 14:08Demo setup and API Gateway
- 19:59Versioning with API Gateway
- 23:32Deprecating old API routes
- 25:59Client registration incentives
- 27:44Custom plugin for rate limiting
- 31:25Testing in production
- 34:38Canary releases
- 35:42Retiring deprecated APIs
- 37:48Summary 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
41mEvolving your APIs, a Step by Step Approach
35mAPISIX, an API Gateway the Apache way
46mEvolving Your HTTP APIs: A Multi-Step Approach
42mEvolving Your HTTP APIs, a Step-by-Step Approach
