Poor API design is not sustainable.
summary
Poor API design raises operating and delivery cost, causes documentation to drift, and fragments implementations — one case condenses six versions into one to save effort. Code‑first workflows skip contracts; design‑first uses a contract, Gravitee visual designer demo builds a mortgage endpoint in minutes and publishes a mock service so frontend and backend run in parallel. Static analysis and linting produce security/quality/compliance scores that block bad specs in CI/CD and prevent broken APIs reaching production.
AI-written summary · about
chapters (4)
related talks
15mAPI Design Lifecycle
30mAPI Code First vs Design First
35mBuilding Your API for Longevity
21mScaling API Design
49mBuilding Software Better: API Lifecycle Management for Developers
43mWhy You Should Be Doing Contract-First Development
33mDesigning Sustainable APIs
27mThe API Design Strategy You Need for Growth