Don’t Remove the API
summary
Argument: don’t remove the API; migrate with a plan and instrumentation instead. Presents a five-step process: define a plan, create the replacement, compare endpoints, notify and track progress, then deprecate. Uses tooling like New Relic/Dynatrace, OpenSearch/logs and Swagger to discover consumers and validate responses. Enforces three deadlines (early adopters, internal, external), tracks progress in a shared doc, emits a sunset header, throws exceptions on unused endpoints, stops staging first and finally redirects or rejects production requests.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker intro
- 1:27Context and migration challenges
- 9:01Five-step migration plan
- 10:51Defining goals and finding consumers
- 13:23Deadlines and consumer types
- 15:32Migration strategy details
- 17:17Tracking progress and responsibilities
- 20:47Deprecation process steps
- 22:38Creating and validating new microservices
- 23:41Communicating with consumers
- 25:29Final deprecation and best practices
- 27:15Q&A and closing
related talks
21mIntroducing The API Lifecycle
41mEvolving your APIs, a Step by Step Approach
46mEvolving Your HTTP APIs: A Multi-Step Approach
28mAPI Productisation - shift RIGHT to Better Product Resilience
30mEvolving your APIs, a step-by-step approach
42mEvolving Your HTTP APIs, a Step-by-Step Approach
25mAPI Security Deep Dive: Safeguard Your Digital Assets
41mREST API refactoring.