Taming the beast - How to manage multiple API platforms at once
summary
Companies already run multiple API platforms and 30% of big enterprises use three platforms, which raises uptime and governance pain points. Three strategies are evaluated: do nothing, replace with one platform (temporary), or front with a proxy (adds a failure layer); the recommended divide-and-conquer: central management + multiple runtimes keeps one developer portal and policy store while letting runtimes handle traffic. Immediate fixes: store APIs as code in git, scan repos for specs and compliance, and deploy via CI/CD; a two-platform management rollout targets 2022.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:28How To Manage Multiple Api Platforms at Once
- 2:41Future of Software
- 2:53Current Trends in the Market
- 6:28Basic Setup
- 7:35Developer Experience
related talks
27mLatest Trends in API Management in 2019
16mBuilding Future-Proof API Platforms
19mMastering Multi-API Gateways: Strategies for Scale, Security & Success.
26mMastering API Strategies for Digital Transformation
29mImpact of Microservices Architecture on API Management
21mAPI platform: Building the business case to support the strategy
25mRunning a Successful API Program: Best Practices and Challenges
23mFederated API Management - The next iterations