Enterprise API management in agile integration
summary
Shows a concrete integration stack: API gateway + API manager + developer portal deployed on kubernetes / OpenShift with CI/CD and GitOps for automated deployments. Recommends treating API config as code (OpenAPI + deployment and gateway configs), enabling self-service publishing, lifecycle/versioning, and hybrid on‑prem/cloud topology. Calls out operational checks — benchmark gateway latency and aim for 5–7 ms overhead target — and stores policies, analytics and SLA reporting in the platform to support secure, discoverable public, private and internal APIs.
AI-written summary · about
chapters (9)
- 0:00Start
- 4:27API Management & Agile Integration
- 5:28API MANAGEMENT KEY CAPABILITIES
- 15:24API MANAGEMENT ARCHITECTURE
- 20:32DEPLOYMENT MODELS
- 21:13DEPLOYMENT ENVIRONMENT
- 22:07API MANAGEMENT AS CODE
- 24:21CITOPS & KEY BENEFITS
- 26:06GITOPS & CONTINUOUS DEPLOYMENT
related talks
25mThe Future of API Management with Everything as Code
27mLatest Trends in API Management in 2019
24mLeveraging Gateway API for Kubernetes Native API Management
28mAPI Gateway: critical component of your digital architecture
23mDecentralized API Management for Agile Enterprises
26mGrowing an API Culture
19mMastering Multi-API Gateways: Strategies for Scale, Security & Success.
29mImpact of Microservices Architecture on API Management