The Cloud Foundry Renaissance
summary
Assertion: Cloud Foundry remains the best choice for running thousands of 12‑factor apps at scale because a single CF platform yields far better economy of scale than managing hundreds of disconnected Kubernetes clusters. Kubernetes costs come from lifecycle overhead, multi‑tenancy and missing Open Service Broker API and Marketplace primitives. Migration of large CF estates is a costly lift‑and‑shift. A concrete toolchain is available: Clutch (Apache‑2, Kubernetes‑native, Crossplane-based client/server) exposes service instances, bindings, plans, backup/restore and a generic OSB bridge so CF and K8s can interoperate.
AI-written summary · about
chapters (11)
- 0:00Introduction to Cloud Foundry Renaissance
- 1:05Kubernetes hype and Cloud Foundry struggles
- 3:54Kubernetes challenges for large organizations
- 5:58Why Cloud Foundry still excels today
- 7:26Cloud Foundry oversold expectations
- 8:31Cloud Foundry operational efficiency
- 10:15Coexistence with Kubernetes
- 11:21When to use Cloud Foundry vs Kubernetes
- 12:47Investing in Cloud Foundry future
- 14:12Clutch and data service automation
- 14:33Summary and call to action
related talks
01mCloud Foundry: The Right Tool for the Right Job
02mCloud Foundry
31mCloud Foundry and Microservices: A Mutualistic Symbiotic Relationship
31mPut Your Money Where Your CF Is
01h 02mCloudFoundry or Kubernetes/Kubo: Choosing the Right Platform for the Job
14mShaping the Cloud Native Future
19mKeynote: 5 Years of Cloud Foundry at Rakuten
37mWhy Do I Need Kubernetes When I Already Have Cloud Foundry? - Sanjay Patil, SAP
