APIs Without Borders: Exploring the world of Locationless API Management
summary
Locationless API management uses Scupper routers and tokens to create a bidirectional Layer‑7 mesh that makes remote endpoints appear local to a single gateway. A live setup links three environments (AWS OpenShift, Azure OpenShift, RHEL VM), exposes remote backends as virtual services, and lets a Red Hat 3scale gateway discover and call them over a single TLS port (443). Calls authenticate with API keys, and Scupper provides automatic load‑balancing and failover; the demo builds and works end‑to‑end.
AI-written summary · about
chapters (12)
- 0:00Locationless API management intro
- 3:38Dispersed API challenges
- 7:28Goals of locationless API management
- 8:55Scupper virtual networks
- 15:41Demo setup overview
- 21:05Scupper network connectivity
- 25:12Exposing APIs across envs
- 27:23API Gateway integration
- 28:51Testing access & auth
- 29:36Load balancing & failover
- 31:20Use cases & benefits
- 32:02Q&A
related talks
23mDecentralized API Management for Agile Enterprises
25mAPI Management - THE key differentiator in digital markets
27mAPIs beyond datacenters: Architecture and Best Practices
26mWhere API management meets the service mesh
27mEnterprise API management in agile integration
34mProxies, Gateways, and Meshes: Cloud Connectivity 101 for...
12mThe Next API Frontier: Mastering API Consumption Across Distributed Envts
29mImpact of Microservices Architecture on API Management
