Not Only for Giants: The Minimal Reasonable Size of a Cloud Foundry Implementation
summary
Argues a workable Cloud Foundry stack for small/medium businesses that shrinks an 18‑VM micro BOSH deployment down to about 4–5 VMs by colocating jobs, isolating the Diego/runner, and offloading services to managed IaaS: micro BOSH on AWS, 18 VMs→5 VMs, replace blobstore with S3, router with ELB and Postgres with RDS. Targets development, testing and light internal production (about 16 containers), omits full HA/load balancing, and estimates cost at ~$300–$400/month depending on instance sizes.
AI-written summary · about
chapters (13)
- 0:00Introduction to Cloud Foundry
- 1:26Small businesses and limitations
- 5:40How Cloud Foundry helps
- 10:38Minimal Cloud Foundry deployment goals
- 12:27Deployment options and Bosh
- 14:16Costly default AWS deployment
- 15:39Trimming the deployment size
- 20:40Sizing the minimal deployment
- 24:52Cost reduction results
- 25:35Future stress testing plans
- 27:26Scaling and downsizing challenges
- 30:56Open sourcing the setup
- 32:19Wrap-up and resources
related talks
10mCost Optimization in Cloud Foundry Through Economies of Scale
20mTaking Cloud to Extremes: Scaled-Down, Highly-Available, and Mission-Critical
48mCloud Foundry - your PaaS on OpenStack
31mA Developer’s Perspective on Cloud Foundry Operations: One Month in the Trenches
28mHow to Deploy CF and Other Bosh Releases on Bare-Metal Environment
23mCloud Foundry and OpenStack
35mResource Management Ecosystem and Cloud Foundry - A Review of the State of the Art
38mWhat Does It Take to Run Cloud Foundry at Enterprise Scale?