Contract-first Principle in Working with APIs
summary
Explains the contract-first approach for frontend–API development: use API contracts to develop frontend in parallel with backend, create abstractions and mocking of the data provider, and handle API version changes so business logic doesn't break. Covers techniques to speed network-related code and workflows that prevent integration failures and maintain good collaboration with backend engineers.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:52API problems without contracts
- 4:18Contract-first principle
- 5:42OpenAPI and Swagger benefits
- 8:52Code generation from contract
- 12:04Design APIs upfront
- 16:17Contract-first bonuses
- 24:41Data vs transport models
- 27:09When to adopt contract-first
- 32:31Frontend and backend sync
- 36:28Avoiding team conflicts
- 38:59API contract validation
- 41:05Contract in workflows
- 42:12Conclusion and Q&A
related talks
43mWhy You Should Be Doing Contract-First Development
30mAPI Code First vs Design First
49mPoor API design is not sustainable.
30mHow to Win Friends with API First
15mAPI Design Lifecycle
26mRevolutionizing Business with API-First Strategy: Key Insights
18mPrototype-first - a modern API development workflow
30mDelivering API First: Is Your API a First Class Citizen?