Keynote: User Panel
summary
Companies describe moving production apps onto Cloud Foundry (backed by SAP Cloud Platform and Pivotal) after starting in 2013, getting a first app live in 2–3 weeks and migrating legacy services over months. The platform runs across three internal data centers and three AWS regions. Pain points: removed CLI access, built a web portal, need finer-grained rollback and RBAC, and faced security/audit integration work. Result: faster experimentation, better developer onboarding, and a clear recruiting advantage.
AI-written summary · about
chapters (16)
- 0:00Introduction and panelists
- 1:02Why use Cloud Foundry
- 3:07Developer productivity gains
- 5:56Developer experience insights
- 8:06Onboarding developers to the platform
- 10:10Cultural shift challenges
- 13:07Developer resistance and change
- 15:12Overcoming initial fears
- 16:58Building vs partnering with vendors
- 19:28Cloud Foundry for SMBs
- 21:57Scalability and budget benefits
- 22:40Biggest missteps and challenges
- 24:23Security and risk management
- 25:28Community needs and future
- 26:55Future of Cloud Foundry
- 27:16Hiring opportunities
related talks
13mKeynote: Leveraging Cloud Foundry for Development Efficiencies
21mKeynote: Cloud Foundry at Rabobank after 10 months of real use
30mKeynote: Enterprise is the New Black
17mKeynote: Cloud Foundry: The Open Community's Model Citizen
26mKeynote: A Platform for the Enterprise: Where Maturity and Innovation Intersect
16mCloud Capabilities Through an Enterprise PaaS
21mKeynote: Enterprise-Ready Lessons for Building Multi-Cloud Apps
11mKeynote: Steampunk Meets Cyberpunk: The Makings of a Cloud Native Application Platform