The docker project evolved out of the PaaS movement, unlocking polyglot cloud-native applications. But it was only a piece of the puzzle to enable platforms, applications and a broader ecosystem. What lessons can be learned from the docker ecosystem?

SHOW: 505

SHOW SPONSORS:

• See how O’Reilly online learning can help your tech teams. Request a free demo now.
• Zesty Homepage - Real Time Cloud Savings
• Free cloud cost-savings evaluation from Zesty

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

CHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"

SHOW NOTES:

• Solomon Hykes shows “docker” at PyCon for 1st time (2013)
• Solomon Hykes on Eps.97, introducing “Docker” (2013)
• History of Docker, Inc (Wikipedia)
• dotCloud becomes Docker (2013)
• Ben Golub (Docker CEO) on Eps.143
• Diverging Container Standard (Kelsey Hightower, OCI, etc.) - 2016
• Introducing Kubernetes Container Runtime Interface (CRI) - 2016
• Microsoft rumored to be buying Docker for $4B (2016)
• Moby Project announced (2017)
• Docker Networking with Socketplane (pre-acquisition by Docker)
• Architectural Considerations for OSS PaaS and Container Platforms (2016) 

HOW DID docker/DOCKER EVOLVE?

Between 2008 and 2013, dozens of PaaS platforms emerged. Within the platform, they all had a model for allocating compute resources, mostly through the use of Linux LXC and cGroups -- what would become containers. dotCloud was the PaaS company started by Solomon Hykes that eventually became Docker. 

LESSONS LEARNED FOR THE FUTURE

• Containers were a fundamental building block for next-gen applications and platforms.
• Docker/docker created a massive community of users, but frustrated the ecosystem of partners. 
• Project / Company naming conflicts are very hard to resolve (“docker” vs. “Docker”)
• Successful ecosystems allow a broad set of participants to monetize different elements of the technology. Not having a monetization model is not a good plan. 
• Docker was the last software company to not monetize through offering a managed/SaaS cloud service. 

FEEDBACK?

• Email: show at thecloudcast dot net
• Twitter: @thecloudcastnet