Scaling OpenAPI in an API-First Company
summary
A Flussonic team describes adopting an API-first approach and scaling OpenAPI 3.1 across a polyglot backend (Erlang, Go, Python, Rust, Rails, C, Node.js) to enable growth. The talk covers using OpenAPI 3.1 for communication between complex services and the practical experience of rolling it out in a high-load company.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:48What is OpenAPI
- 8:36OpenAPI implementation
- 17:35Codification principle
- 24:38Unified language
- 31:43Process changes
- 36:43Contract versioning
- 40:16Q&A
related talks
25mAPIs for Scaling Enterprises: Setting and Applying API Standards.
05mAPI-First Development: Future-Ready Systems
36mOne to millions - opportunities and challenges in scaling APIs.
16mAPI-First Development with OpenAPI — You Should Practice It!?
39mAPI Development in 2017
30mAPI Code First vs Design First
41mWhy your company needs an internal API and what you should do about it
48mTransforming a monolith to an API platform