API Versioning for Zero Downtime
summary
ING builds an API platform that separates API (interface) from service (implementation), makes an API endpoint the atomic routing key, and uses an API registry plus service discovery so instances register at runtime. The platform stores a manifest pinning the exact OpenAPI spec version and issues subscription tokens, enabling client‑side load balancing and safe canary rollouts. The concrete claim is zero‑downtime deploys via version‑pinned routing; the system is already implemented and used inside ING.
AI-written summary · about
chapters (12)
- 0:00Start
- 5:45Versioning of of Api
- 10:47Api Specification
- 13:24Semantic Versioning
- 18:04Service Discovery
- 26:08Server-Side Load Balancing and Client-Side Load Balancing
- 27:17Self Provisioning System
- 38:02Api Sdk
- 39:32What Is a Cannery Release
- 44:21Subscribe to the Api Endpoints
- 46:59Summary
- 48:12Final Conclusion
related talks
50mAPI Versioning for REST: In Real Life, How Do We Do It?
21mAPI Discovery done right: Engaging the right people with your APIs.
22mBuilding Reliable APIs with Apache APISIX
20mKeynote ‘Bullet-proofing APIs to build reliable systems’
42mThe future of API (Platform) architecture
25mAPI Management - THE key differentiator in digital markets
28mAPI First to the Extreme - Federated API Design via Inner Sourcing
43mAPIs Are the Backbone of Every Company