Decentralized API Management for Agile Enterprises
summary
Proposes a cell-based architecture where each cell packages services, data and a local micro gateway runtime generated from OpenAPI (or similar) so gateways live next to services instead of one central gateway. Shows protocol switching (HTTP↔gRPC), on‑the‑fly XML→JSON transforms, and local enforcement of auth and throttling while sending async telemetry to a control plane. Claims lower latency and resource use versus synchronous key‑manager calls; example flow uses traffic controller to revoke access after ~1,000 requests.
AI-written summary · about
chapters (8)
- 0:00Decentralized API management
- 1:06Traditional API gateways limits
- 4:06Cell-based architecture for scalability
- 7:24Bottom-up API delivery with micro gateways
- 10:38Protocol support and message transformation
- 12:46Policy enforcement and observability
- 15:39Cellular architecture benefits
- 16:42Q&A on traffic control
related talks
06mHow to be API-centric and microservice friendly
27mEnterprise API management in agile integration
26mAPI-Driven Microservice Architecture: Empowering Digital Transformation
29mImpact of Microservices Architecture on API Management
28mAPI Gateway: critical component of your digital architecture
27mMaster API Gateways: Boost Your Microservices Strategy
32mAdopting a Modern API Strategy for Hybrid, Multi-Cloud Architectures
26mTake control of your microservices with App Mesh