Why we Picked CF as the Basis for our Public Cloud Multi-Tenant Platform
summary
Public multi-tenant content platform uses Cloud Foundry and BOSH with Warden containers, Cassandra, XDB, Swift and RabbitMQ, deployed into six isolated networks; an automated CI/CD pipeline pushes builds to production in about 12 hours and runs weekly. An upgrade tool performs blue-green upgrades tenant-by-tenant and also reconfigures microservices, giving zero-downtime migrations. Production proves the approach: 29 full releases in 37 weeks, automatic patching of roughly 500 VMs during the Shellshock stemcell update, and operational scaling and logging handled by CF without bespoke VM orchestration.
AI-written summary · about
chapters (17)
- 0:00Introduction and team
- 2:08Why multi-tenant platform
- 8:09Production setup and architecture
- 11:02Network partitioning for security
- 13:07Why Cloud Foundry and BOSH
- 15:14Automated upgrades and Shellshock
- 17:00Cloud Foundry API and blue-green deployments
- 21:56Upgrade tool and tenant migration
- 24:02Challenges and CLI changes
- 25:27Open-source contributions and focus
- 26:51CI/CD environments and testing
- 29:00Deployment history and agility
- 31:48Release model and roadmap
- 32:10Q&A: Stem cells and Warden vs Docker
- 33:56Q&A: Multi-tenancy approaches
- 36:47Q&A: Privacy and compliance
- 37:48Q&A: Resiliency testing
