Nicolas Fränkel
Evolving your APIs, a step-by-step approach
#1about 1 minute
The challenge of evolving APIs without breaking changes
Evolving an API is difficult because initial development focuses on domain modeling, not long-term versioning strategies.
#2about 5 minutes
Using an API gateway instead of a reverse proxy
An API gateway is a specialized reverse proxy that handles modern, complex requirements like dynamic configuration and client-specific rate limiting.
#3about 4 minutes
Setting up the initial proxy route with Apache APISIX
The first step is to configure the API gateway to proxy requests to the existing upstream service without any downtime.
#4about 3 minutes
Creating a versioned route with path rewriting
Introduce a versioned path like /v1 and use the API gateway to rewrite the request path before forwarding it to the upstream service.
#5about 1 minute
Redirecting legacy endpoints using an HTTP 301 response
Deprecate the old, unversioned endpoint by configuring the API gateway to return an HTTP 301 permanent redirect to the new versioned URL.
#6about 5 minutes
Implementing rate limiting to encourage user registration
Use a custom Lua plugin to enforce rate limits on unauthenticated users, prompting them to register to get an API key for unlimited access.
#7about 2 minutes
Canary releasing the new API version with traffic splitting
Safely roll out the new API version by configuring the gateway to split a percentage of production traffic between the old and new upstreams.
#8about 2 minutes
Deprecating an old API version using HTTP headers
Formally deprecate the V1 endpoint by adding Deprecation, Link, and Sunset headers to the response, guiding clients to the new V2 endpoint.
#9about 6 minutes
Q&A on API versioning and management strategies
The audience asks questions about rate limiting per token, managing multiple versions, reverting changes, and the definition of API management.
Related jobs
Jobs that call for the skills explored in this talk.
Matching moments
11:05 MIN
Evolving an API without versioning using a fallback pattern
Designing gRPC APIs - The things they don't tell you
00:05 MIN
The challenges of building and maintaining APIs
API = Some REST and HTTP, right? RIGHT?!
14:08 MIN
A practical guide to deprecating old API versions
API = Some REST and HTTP, right? RIGHT?!
40:46 MIN
Q&A on adopting new web APIs
Explore new web features before everyone else
08:09 MIN
Tracing the evolution of APIs from RPC to GraphQL
The Great API Debate: REST, GraphQL, or gRPC?
27:31 MIN
The cyclical nature of API design and development
Awful APIs: A History Lesson in Industry Mistakes and Mishaps
03:41 MIN
Why learning about new APIs benefits developers
Explore new web features before everyone else
00:39 MIN
The promise versus the reality of using APIs
Develop, test and run a communications application in a serverless cloud
Featured Partners
Related Videos
28:55Awful APIs: A History Lesson in Industry Mistakes and Mishaps
James Seconde
20:29REST in Peace? What does the API protocol of the future look like? Or do we have it already?
Simon Auer
29:30Lessons from Our API Past: Evolving to a Resilient API Future
Yousaf Nabi
27:17Designing gRPC APIs - The things they don't tell you
Bastian Eicher
27:25API = Some REST and HTTP, right? RIGHT?!
Rustam Mehmandarov
23:47Lessons learned from observing a billion API requests
Pratim Bhosale
28:16The Great API Debate: REST, GraphQL, or gRPC?
Alexis Yushin
44:15API Design - Getting Started
Alen Pokos
Related Articles
View all articles
From learning to earning
Jobs that call for the skills explored in this talk.
(Senior) Full-stack Developer (Next.js / Node.js)
OKAPI:Orbits GmbH
Senior
GIT
WebGL
Docker
MongoDB
Node.js
+7
(Senior) Full-stack Developer (Next.js / Node.js)
OKAPI:Orbits GmbH
Senior
GIT
WebGL
Docker
MongoDB
Node.js
+7
APIs Project Manager
ferrer