Navigating the Cloud Foundry Ecosystem of Ecosystems: An ISV Perspective
summary
Iron.io joined the Cloud Foundry Foundation to offer a containerized, event‑driven job platform (founded 2011, ~50 people) and integrates via a service broker to provision services, is packaging deployables for Bosh, and is working toward native runtime integration with the Diego tasks API so tasks spawn as Diego tasks instead of raw Docker containers. Integration required Cloud Controller API hooks for logging/monitoring, influenced Diego roadmap, and targets parity with AWS SQS/Lambda for multi‑cloud customers.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 1:20Ironio
- 2:10Ecosystems
- 3:00Independent Ecosystems
- 3:41Multiverse
- 4:10Interoperability
- 5:33Digital Transformation
- 5:58Continuous Innovation
- 6:41Entry Point
- 6:57Distributions
- 7:32Building workloads
- 9:02Cloud Foundry reference architecture
- 9:42Overlap
- 10:40RFPs
- 12:20Why Ironio joined Cloud Foundry
- 13:44What to bring to the table
- 14:10Why you should care
- 16:27Cloud Foundry opinionated platform
- 17:00Interface with Cloud Foundry components
- 19:18Package integration
- 20:44Technology partnership
- 21:05Product fit
- 22:14Joint initiatives
- 23:09Interoperability aspirations
- 24:15Is Cloud Foundry opinionated
- 25:06Cloud Foundry strengths
- 25:54Personal note
related talks
23mKeynote: Zen and the Art of Platform
03mCloud Foundry
33mDocker and Cloud Foundry: The 3 Use Cases
09m.NET and Iron Foundry Incubation: It's coming!
08mIntroduction to the Cloud Foundry at Scale Track - Julian Fischer, anynines & Matthias Steiner, SAP
32mCloud Foundry Diego Update
33mCase Study: Orange Labs & Cloud Foundry
20mWelcome Remarks - Abby Kearns, Executive Director, Cloud Foundry Foundation