Managing the Complexity of Microservices Deployments - Prithpal Bhogill, Google & Kenny Bastini
summary
Shows how Cloud Foundry plus Apigee Edge and Spring Boot/Spring Cloud Services create a deployable reference architecture: a 10‑service storefront example uses an API gateway to present a single contract while backend services remain independent; integration uses a CF service broker (on PivNet), route services to auto-create API proxies, and a tiny microgateway that can be co‑resident with app containers; uses a gateway cache pattern, >30 out‑of‑the‑box policies, analytics and gradual Strangler migration to move data off legacy systems.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:37We started with the monolith
- 4:56We have now arrived at microservices
- 6:00Cloud Native Microservices
- 7:02Microservice API Gateway Pattern
- 7:24Strangling the Monolith
- 9:33Legacy Edge Adapter Pattern
- 11:11Pivotal Cloud Foundry
- 11:56Microservice vs API
- 12:48APIs and Microservices are complimentary
- 13:33APIs shield consumers from Microservices
- 15:05Every API has a lifecycle
- 16:37Apigee API Platform
- 18:39Apigee provides the API layer for Microservices
- 19:28Integrated offerings - Flexibility & Choice
- 22:42Use API Management as you transition to Microservices
- 24:27Solution Benefits
related talks
01h 04mManaging the Complexity of Microservices Deployments
31mDeploying Microservice Architectures with Cloud Foundry
01h 29mDeveloping Microservices for PaaS with Spring and Cloud Foundry
31mCloud Foundry and Microservices: A Mutualistic Symbiotic Relationship
22mPanel: The Microservices Stack: Are We There Yet? What’s Missing?
41mLiving on the Edge (Service): Bunding Microservices
39mA Decentralized Reference Architecture for Cloud-native Applications
23mMicroservices Architectures: Agility vs Complexity