Unlocking API Potential: Design First Approach
summary
Argues that starting from design cuts future updates and auto-generates runtime artifacts, with a Swagger generator that auto-produces client and server code plus database setup. Describes a working travel-condition verifier that accepts uploaded vaccine/test documents, cross-checks a second source and returns a compliance status, covering 44 modalities of entry rules. Outlines a repeatable, domain-agnostic design methodology that maps resources, contracts and semantics so teams can reuse the same Design First workflow across products.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:02Introduction Overview
- 0:28Initial Design Concepts
- 6:12Verifying Travel Conditions
- 14:32Explaining Open API Definition
related talks
30mAPI Code First vs Design First
37mWhy to Use Design First and Server Side Swift if Everything Works Anyway
27mUnlocking API Success: Bridging Business & Engineering
17mAPI Security Simplified: Practical Tips & Tools
49mPoor API design is not sustainable.
43mWhy You Should Be Doing Contract-First Development
18mFive Essential Design Assets for Successful APIs
25mThe Life Changing Magic of Becoming API First