What does it mean to create API products at scale?
summary
Firebase runs 15+ products across 6+ platforms and manages 100+ API services by enforcing a documented change process that averages under two weeks, handled by an API council of five with a three-member quorum and over 160 proposals/year. A real-world break/change: the v9 JavaScript SDK rewrite cuts payloads up to 85% and ships with a compatibility layer after a two‑year rewrite. Practices include AIPs (google.aip.dev), an automated linter, required approvals and the ability to block launches to keep APIs stable.
AI-written summary · about
chapters (12)
- 0:00API products at scale
- 1:06Process and governance for APIs
- 3:33Keeping API quality over time
- 6:20Forces degrading API quality
- 8:29Firebase’s API governance
- 13:21Reviewing API proposals
- 15:23Enforcing API governance
- 16:05Scaling governance for services
- 17:49Style guides for API design
- 18:33Keeping APIs good with complexity
- 19:38Outcome of API governance
- 20:20Q&A
related talks
25mThe API Revolution bring us to continuously change
23mContinuous API Product Management
56mWhat are the means to accelerate the API strategy
28mAPI Productisation - shift RIGHT to Better Product Resilience
26mBuilding successful API developer programs
27mApidays Virtual Helsinki - Geir Sjurseth, Google Cloud
14mHow to build better and consistent APIs at scale
54mAPI's a drivers for innovative business models