Evolving your APIs, a step-by-step approach
summary
Demo uses Apache APISIX (Nginx-based) with etcd, Docker Compose, Prometheus and Grafana to walk a migration: create routes/upstreams, rewrite v1/v2 path, add a 301 redirect plugin, enforce registration via a custom Lua rate‑limit plugin that exempts authenticated consumers (api_key header), mirror live traffic with the miraproxy before rolling to a split‑traffic canary, observe error rates on dashboards, and retire endpoints with Deprecation/Sunset headers; custom plugin takes a few hours to implement.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:45About Nicolas
- 1:20First time creating APIs
- 2:10Compatibility
- 2:33Initial situation
- 2:46API Gateway vs API Getaway
- 3:23Demo
- 7:31Creating a new route
- 12:22Making users register
- 15:54Store testing
- 17:25Canary release
- 21:15Multiple versions
- 24:59Questions
related talks
44mEvolving Your APIs, A Step-By-Step Approach
41mEvolving your APIs, a Step by Step Approach
49mEvolving your APIs, a step by step approach
35mEvolving 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