10 Lessons We Learned with Cloud Foundry - Neville George, Comcast
summary
Comcast runs Pivotal Cloud Foundry for four years across 12 foundations, migrates a billing monolith to 65–70% on CF, and grows a 1,000-member Slack community that answers most support questions. Tooling includes GitHub markdown docs with a pipeline, Influx/Telegraf/Alerta for monitoring, and limited data services (RabbitMQ, Redis). Platform work cuts tickets by about 85%, publishes live metrics, and ships a homegrown GSLB as a service that drops GSLB provisioning from 15–45 days to five minutes.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:29Find a champion
- 3:16Be ambitious
- 5:04Lower the bar
- 6:50Define guardrails
- 8:14Support services wisely
- 10:24Reinforce platform rules
- 10:46Build community support
- 13:15Establish trust
- 15:21Crowdsource documentation
- 17:09Control your destiny
- 19:19Adopt open source tools
- 20:43Collaborate with teams
- 22:08Create your own services
- 26:41Q&A session
related talks
23mKeynote: How Comcast is Putting Customers First - Powered by Cloud Foundry
47mComcast Cloud Foundry Journey
23mThe Genesis of Cloud Foundry: Using Open Source Tools to Easily Deploy...
08mKeynote: How Comcast is Working to Transform our Product Delivery Experience
32mStories of Growth and Competitive Edge with Cloud Foundry
38mWhat Does It Take to Run Cloud Foundry at Enterprise Scale?
25mChanging the Development Culture at Comcast and Our Evolution from Legacy SOA to Cloud Native
06mLightning Talk: Experiences with CF as the Main Target Platform for our Company