Public Cloud Foundry Platforms in Europe: What Have We Learned and Where Can We Go Next?
summary
Panelists report running public CF on VMware, OpenStack and AWS, using Concourse for CI and PWS/PCF for dogfooding while juggling differing CF API cadences, billing integrations and security CVE patches. A Bluemix deployment adds ~20,000 users/week; one customer cuts seasonal infra cost from $98,000 to $200 by moving to a public CF. Missing items are isolation segments for bursty workloads, data‑center awareness and EU data residency, and a shared service marketplace and common data services to make CF pushes portable.
AI-written summary · about
chapters (14)
- 0:00Introduction to panel
- 1:03Panelist introductions
- 3:13API version differences across platforms
- 7:57Desired Cloud Foundry features
- 11:09User perspective on public CF
- 13:23Service marketplaces and lock-in
- 16:51PWS as a testing ground for PCF
- 17:52Economic viability of public CF
- 22:04Startups vs enterprises on CF
- 24:59When to use own Cloud Foundry
- 27:20Audience Q&A on PWS services
- 28:46Improving the marketplace
- 30:30Growing European Cloud Foundry
- 32:17Seamless multi-cloud transitions
related talks
33mCloud Foundry Weekly: Live at CF Day Germany
17mKeynote: Cloud Foundry: The Open Community's Model Citizen
48mCloud Foundry - your PaaS on OpenStack
31mPut Your Money Where Your CF Is
09mEnterprise-Ready PCF - Making The Cool Super Cool
06mHybrid Clouds and Cloud Foundry
30mCloud Foundry: The Gaps
27mCloud Foundry Compared with Other PaaSes