A Roadmap to Active Multi Cloud
summary
Claim: running multiple Cloud Foundry installations that appear as one is practical if data and identity are separated and automated. BOSH deploys CF to different clouds, Route53 or latency load balancing routes users, Concourse enforces a Concourse-driven declarative source of truth to sync orgs spaces users and apps, and teams use ephemeral Cloud Foundry instances with blue/green deploys. Hardest part is SQL-backed app data and tokens so teams adopt eventual consistency window is small, distributed stores (Cloud Spanner Redis RDS) and user-provided service instances for production.
AI-written summary · about
chapters (6)
- 0:00Introduction to active multi-cloud
- 3:31Use cases for active multi-cloud
- 7:23Data challenges in multi-cloud
- 13:07Solutions for identity and app data
- 15:54Best practices and automation
- 18:43Q&A session
related talks
29mMulti-DC Cloud Foundry: What, Why and How?
30mLiberate Your Cloud Foundry Installation From Being Constrained to a Single Cloud
40mThe Rocket Science of Deploying Cloud Foundry in Multi-Cloud Environments
28mManaging Multiple Clouds with a Single BOSH Deployment
29mSetting up a Multi-Cloud, Enterprise-Grade Cloud Foundry Installation: Bridging Infrastructure
20mDesigning for Multicloud
31mPut Your Money Where Your CF Is
48mCloud Foundry - your PaaS on OpenStack