Enhancing Governance, Cost Efficiency, and Developer Productivity.
summary
Schneider Electric migrates from a centralized API team to a federated model supporting ~30 teams and 150 APIs, handling about 70 million API calls/month. Two delivery paths exist: CI/CD self‑service for less mature teams and dedicated tenant access for mature teams, with central enforcement of global policies. Infrastructure cost falls by scaling a single gateway instead of duplicating instances, and platform deployment effort drops from about 500 hours per quarter toward near zero as teams onboard.
AI-written summary · about
chapters (10)
- 0:00Federated API management intro
- 1:11Schneider Electric’s ecosystem
- 3:47Centralized API management challenges
- 9:09Adopting federated API model
- 12:45Security and governance
- 16:43Cost efficiency via scaling
- 18:33Transitioning to federated processes
- 21:09API team maturity solutions
- 24:05Outcomes and productivity
- 26:37Future federated API catalogs
related talks
25mThe API Revolution bring us to continuously change
26mGrowing an API Culture
25mTransforming the enterprise with APIs
27mEnterprise API management in agile integration
56mWhat are the means to accelerate the API strategy
21mAPI Governance as an enabler of an architectural evolution The SNAM experience
26mFostering API Productization in Federated API Architecture
26mScaling API Re-Use, Security & Integration Across the Multi-Property Consortia.