The Future is Easy, Naming Things is Hard
summary
Origins of Cloud Foundry start as project B29 with a prototype in three months and a runtime called the droplet execution agent later replaced by Diego; VM lifecycle tooling becomes BOSH for infrastructure provisioning. Early demo launches 100 Node apps in nine seconds and first customer is Salesforce; initial language is Ruby then shifts to Java as ecosystem demands change. Current claim is that progress splits into three practical buckets — infrastructure provisioning, artifact to workload, and workload orchestration — and standard interfaces plus policy are the remaining problems.
AI-written summary · about
chapters (22)
- 0:00Intro
- 1:07About me
- 1:39Project B29
- 4:37Heroku
- 6:19Cloud Foundry
- 7:37VMware at Open Source
- 9:46Fun Facts
- 12:43Salesforce
- 16:23First Marketing Person
- 16:56Wired Photo
- 18:02What We Got Right
- 19:43What We Got Wrong
- 23:45What You Got Right
- 25:01Whats Next
- 25:29Solving World Hunger
- 28:35Buckets of Technologies
- 29:24The 80/20 Rule
- 29:53Standardization
- 30:43Open Cloud Ecosystem
- 31:03Defining Ecosystems
- 33:02Working Together
- 33:36Conclusion