Introduction to API Drift
summary
API drift means implementation diverges from documentation — proof: a websocket-based collaborative drawing app wired to FastAPI shows connections jump from 1 to 2 and real-time drawing works only when contract matches implementation. The demo uses an AsyncAPI parser validation that rejects messages with unexpected fields (no additionalProperties), showing how design-first spec-driven codegen plus GitHub Actions, schema registries and generated docs prevent broken integrations and reduce support cost.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:47What is API drift
- 5:01API drift causes
- 7:30Impact of API drift
- 10:21AsyncAPI for event-driven APIs
- 14:21Design-first approach
- 20:47Demo: AsyncAPI app
- 31:59Enforcing contracts with Passer
- 38:40Event drift prevention
- 40:08Best practices
- 43:21Key takeaways and closing remarks








