Why You Should Be Doing Contract-First Development
summary
Argues that writing the API contract first eliminates front-end/back-end waits by letting teams iterate against the spec, then generate code and tests automatically. Workflow: author an OpenAPI YAML, mock it with Prism mock server to build a validated UI (demo uses Vue), publish the spec to a registry (Epicurio), run OpenAPI Generator to emit server interfaces and client SDKs, and use Atlassian request validators to auto-test against the contract. Claims this cuts rework and integration delays.
AI-written summary · about
chapters (7)
- 0:00The challenges of integration
- 2:01Benefits of contract first
- 4:45The contract first workflow
- 6:47OpenAPI specification details
- 14:12Tools for API development
- 20:24Live demonstration
- 35:03Q&A and best practices
related talks
43mContract-first Principle in Working with APIs
30mAPI Code First vs Design First
16mAPI-First Development with OpenAPI — You Should Practice It!?
47mContract-Driven API Development with OpenAPI Specification
25mThe Life Changing Magic of Becoming API First
18mPrototype-first - a modern API development workflow
59mDriving better outcomes through API first development
35mAPI-First! Contract-First! Make API development great again!