The changing API problem
summary
Claims an API‑first workflow using OpenAPI stops surprise breaking changes by generating code, mocks and CI checks. Built a Node.js CLI because Java tools were unacceptable, published openapi-nodejs-cli on npm to scaffold Express server, client code and TypeScript interfaces automatically. A memory mock server starts in ~2s and serves endpoints, validates required fields and rejects extra properties; a validator for CI is in development. Demo shows generated routes return sample data and unimplemented handlers throw clear errors.
AI-written summary · about
chapters (7)
- 0:00API challenges in distributed systems
- 1:21Front-end back-end communication
- 3:16API integration with contract negotiation
- 5:04OpenAPI specification for alignment
- 6:10Automated API scaffolding
- 8:46Live demo: API mock server
- 13:55Tools resources contact
related talks
35mAPI-First! Contract-First! Make API development great again!
25mThe Life Changing Magic of Becoming API First
29mStarting From Scratch
27mBuilding Great Web APIs
44mNode & Express as Workflow Tools
35mFake It Before You Make It: Mocking Your Way to Better HTTP APIs
19mSecure and accelerate APIs' lifecycle with the OpenAPI specification
59mDriving better outcomes through API first development