Using CF Route Services to Publish, Secure and Monitor APIs
summary
Cloud Foundry 1.7 route services let requests be intercepted and transformed before apps see them, enabling an API management stack deployed as an Apigee Edge tile via a service broker that auto-creates an OpenAPI-driven proxy. Demonstrated features include quota enforcement, spike arrests and content caching (GETs hit a cache, POSTs require auth), used by Predix to manage ~30–40 services and hundreds of APIs with rapid developer growth (500%). Current path supports HTTP routing only and operators must watch latency and performance tradeoffs.
AI-written summary · about
chapters (8)
- 0:00Introduction to route services
- 1:34The role of APIs in scaling
- 4:40Understanding route services
- 8:34Operational API management
- 13:18Integrating Apogee and CF
- 15:11Demonstration of features
- 17:51Real-world use case at GE
- 32:34Summary and Q&A
related talks
31mUsing CF Route Services to Publish, Secure and Monitor APIs
26mWrite Once, Earn Anywhere – Monetizing Enterprise APIs with Cloud Foundry
24mCloud Foundry Cookbook
01h 04mManaging the Complexity of Microservices Deployments
42mThe future of API (Platform) architecture
25mHow API-as-a-Service can Improve CX, Scalability, and Security
31mBoF: Security Best Practices in Cloud Foundry
22mPushing the Limits: Cloud Foundry Runtime and Routing at SAP...