Managing the Complexity of Microservices Deployments
summary
Shows a concrete integration: Pivotal Cloud Foundry plus Apigee Edge with an Apigee Edge microgateway sidecar inserted by a decorator buildpack via the new beta 3.0 service broker. Demo config enforces policies (OAuth, spike arrest policy, quotas), reverse-proxies app traffic, and streams analytics to Apigee; rate limiting blocks excess requests in real time. Uses the strangler pattern to migrate data from legacy DBs. Cited customer gains: ~85% faster time‑to‑market and >95% developer productivity.
AI-written summary · about
chapters (8)
- 0:00Introduction to microservices complexity
- 10:59Monolith to microservices transition
- 17:21Apogee and PCF partnership
- 27:02API management for microservices
- 34:52Live demo setup
- 48:10Demo: Securing microservices
- 55:13Key takeaways and benefits
- 1:01:57Q&A and closing remarks
related talks
27mManaging the Complexity of Microservices Deployments - Prithpal Bhogill, Google & Kenny Bastini
54mAppify your service mess(h)
41mLiving on the Edge (Service): Bunding Microservices
25mAPI Management from a Network Engineer's perspective
50mFacilitate development of complex APIs
31mDeploying Microservice Architectures with Cloud Foundry
57mLiving on the Edge (Service): Bundling Microservices to Optimize Consumption for Devices
46mCloud based API gateway or more?