Cloud Foundry and Microservices: A Mutualistic Symbiotic Relationship
summary
Argues Cloud Foundry removes much of the operational tax of microservices by providing buildpacks, containerized runtimes, a CLI and API, service broker plumbing (RabbitMQ, IronMQ, Redis) and VCAP_SERVICE bindings so teams push, bind and scale without writing ops glue. Claims microservices let small two‑pizza teams (≈6 people) own polyglot stacks and polyglot persistence but cost more to operate; CF compensates with health monitoring, fast start/stop, CF scale and manifest-driven deploys. Notes 55% of web traffic is mobile and Spring Boot/Cloud pair well with the model.
AI-written summary · about
chapters (11)
- 0:00Introduction to talk
- 1:06Business disruption driving change
- 4:16Monoliths vs microservices
- 8:11Simple vs easy in software
- 12:31Microservices architecture explained
- 15:21Team structure for microservices
- 19:32Twelve-factor apps and Cloud Foundry
- 23:44Frameworks for microservices
- 24:47Challenges of microservices
- 27:17Cloud Foundry mitigates microservices costs
- 30:45Symbiotic relationship summary
related talks
31mDeploying Microservice Architectures with Cloud Foundry
37mJava Microservices at Scale on Cloud Foundry, Today and Tomorrow
22mPanel: The Microservices Stack: Are We There Yet? What’s Missing?
15mThe Cloud Foundry Renaissance
01h 29mDeveloping Microservices for PaaS with Spring and Cloud Foundry
02mCloud Foundry
31mCloud Foundry Networking: Enabling Direct Communication for Microservices - Chin, McClure
27mManaging the Complexity of Microservices Deployments - Prithpal Bhogill, Google & Kenny Bastini