Keynote ‘Bullet-proofing APIs to build reliable systems’
summary
ING describes a concrete pipeline: generate code from API spec to lock the letter of the contract, then validate the spirit with consumer-driven contract tests used by both consumers and producers, gate deployments with a “can I deploy now” check, exercise critical paths via staging smoke tests to catch config/network issues, and roll out with small canary deploys to limit blast radius. The claim is these steps measurably raise API reliability in their case study.
AI-written summary · about
chapters (10)
- 0:00Introduction and keynote opener
- 1:51Why software reliability matters
- 4:06Communication pitfalls in APIs
- 6:14Compiling API specifications to code
- 8:22Consumer-driven contract testing
- 10:54Tollgate for safe deployments
- 12:22Staging environments for integration
- 14:28Canary deployments in production
- 17:14Combining techniques for assurance
- 19:42Closing and next steps
related talks
49mBuilding Software Better: API Lifecycle Management for Developers
06mKeynote: APIs, the Universe, and Everything
29mAccelerate API Innovation: Secrets to Staying Ahead
16mDo the Right thing, shift Left!
19mMaster API Automation: Proven Strategies & Tools
27mBuilding Great Web APIs
25mBoost API Success: Key to Transparency & Accountability
14mHow to build better and consistent APIs at scale