How API-as-a-Service can Improve CX, Scalability, and Security
summary
Proposes building an internal API cloud that decouples API definition from runtime, automates API lifecycle in CI/CD (Swagger, YAML, Git), and pushes gateway logic close to microservices via a distributed micro API gateway; cites customers hitting 10–15 billion API calls per day and needing 2 million API calls per second peaks while keeping tail latency under 30 ms. Recommends NGINX Controller plus nginx App Protect, treat infrastructure as code for fast rollback, and shift API management left into testing.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:20Digital Transformation
- 4:09Apis
- 10:36APIs as a Service
- 12:05Microservices and APIs
- 15:17What is APIasaService
- 16:59Secure API as a Service
- 20:55Questions
related talks
28mAPI Gateway: critical component of your digital architecture
20mAPI Gateway in a Nutshell
24mAPI Security in DevSecOps: Built-In, Not Bolted On
19mMastering Multi-API Gateways: Strategies for Scale, Security & Success.
21mAPI platform: Building the business case to support the strategy
26mBuilding, Managing & Governing APIs on AWS
19mMastering API Management in the Gen AI Era: Do This Now!
42mThe future of API (Platform) architecture