DiscoverThe CloudcastLessons Learned from Cloud Foundry
Lessons Learned from Cloud Foundry

Lessons Learned from Cloud Foundry

Update: 2021-03-07
Share

Description

Cloud Foundry was going to create an open source alternative to Heroku, as well as replace how Enterprise companies built software. But change is never easy. Looking back, what can we learn from the lessons of Cloud Foundry?

SHOW: 495

SHOW SPONSOR LINKS:

CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotw

CHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"

SHOW NOTES:

HOW DID CLOUD FOUNDRY EVOLVE?

An open source, programmable cloud application platform (PaaS). Heroku (2007), Google AppEngine (2008) existed before Cloud Foundry (April 2011). OpenShift launched in May 2011. Apcera was launched in 2012 by Derek Collison 

  • Open Source, Multi-cloud
  • Multiple languages, frameworks
  • Automation for the infrastructure (BOSH)
  • Integrated Logging, Tracing, Routing, GUI
  • Data Services live off the platform, via Service Broker
  • Very heavy platform footprint (up to 50 VMs)
  • Diego container scheduler 
  • Warden container runtime 

Many large vendors got involved once it became a foundation. 

  • IBM, SAP, Intel, Cisco, EMC/VMware
  • Many end-user customers joined (great for recruiting)
  • None of the Cloud providers, other than an infrastructure stem-cell

By 2016-17, most large Cloud Foundry vendors were shifting their focus to Kubernetes

LESSONS LEARNED FOR THE FUTURE

  • Single-vendor led communities are difficult, especially if a foundation is created.
  • Technology transitions are hard, oftentimes impossible. Cloud Foundry chose to downplay Docker and Kubernetes as “just for infrastructure”, even within their own community. 
  • Make it simple to get environments/clusters (Managed Kubernetes services, Cluster API, laptop-level environments (minikube). Needs to be a managed cloud service on good clouds. 
  • Platform-aware, Infrastructure automation is important (e.g. like BOSH, except that it works)
  • Industry is mixed on if stateful / data services should run on-platform or off-platform. Having to also manage the off-platform is difficult. 

FEEDBACK?

Comments 
00:00
00:00
x

0.5x

0.8x

1.0x

1.25x

1.5x

2.0x

3.0x

Sleep Timer

Off

End of Episode

5 Minutes

10 Minutes

15 Minutes

30 Minutes

45 Minutes

60 Minutes

120 Minutes

Lessons Learned from Cloud Foundry

Lessons Learned from Cloud Foundry

Cloudcast Media