Download to read offline
Uploaded byThe {code} Team
Winter is Coming: Who Will Win The Container Wars (webinar)
The webinar presents an analysis of the competitive landscape in container orchestration, discussing key players like Docker, Kubernetes, and Cloud Foundry while establishing distinctions between 'orchestrators' and 'platforms.' Key lessons include the importance of automation and the operational model of DevOps in advancing maturity in infrastructure. The presenter also shares predictions about the future dynamics within the industry, including potential acquisitions and the sustainability of various projects.
More Related Content
Similar to Winter is Coming: Who Will Win The Container Wars (webinar)
Winter is Coming: Who Will Win The Container Wars (webinar)
- 1. Joshua Bernstein @quityourjoshing github.com/koensayr {code} Webinar:Winter is coming Who will win the Container Wars?
- 2. 2 Disclaimer The statements, views,and ideas contained in this presentation are the sole opinion of the presenter individually and may not reflect the views of the presenter's employer. Any statements of financial information should be taken as pure conjecture and have only been sourced by publically available information.
- 3. 3 Agenda • Introduction andBackground • Lessons of a Past Life • Orchestrators vs Platforms • Who’s Who • The Four Lenses • Perspective • Future Predictions
- 4. 4 Lessons of aPast Life • Dozens of Sites Worldwide • Dozens of Countries • Over One Hundred Thousand Hosts • Largest VMware Environment ever Built • Later the largest Containerized Environment • 100s Millions Req/Day
- 5. 5 Do Something MateriallyDifferent • Maturity of the environment increases as you move up the stack • Skipping levels limits the Infrastructure’s actualization/potential • Automation • No Snowflakes • An abstraction of Infrastructure away from the Applications • Resiliency moves away from Infrastructure and into the Application (Move Up the Stack) • Operational Model (DevOps) Key Principles What Makes It Different
- 6.
- 7. 7 Orchestrators vs Platforms “Anorchestrator is a piece of software that manages the scheduling of a workload demand within a constrained supply of resources” • Workload demand is some unit of work • (ie: tasks, jobs, virtual machines, services, etc) • Resources typically means compute resources • (CPU, memory, storage, network, etc) • Examples include • Docker Swarm • Apache Mesos
- 8. 8 Orchestrators vs Platforms “Anplatform is a collection of software that provides orchestration in addition to desired supplemental services” • Supplemental Services • Service Discovery • Storage Services • Network Abstraction (Even Segmentation) • Source Control Integration • Examples Include • Kubernetes • Mesosphere DC/OS • Cloud Foundry • OpenShift
- 9.
- 10. 10 Who’s Who • TheFour Horsemen – Docker Swarm – Cloud Foundry – Kubernetes – Mesosphere DC/OS • Supporting Cast – Nomad – Serf – Rancher – <insert your favorite here>
- 11. 11 The Four Lenses •Economic Lens • Focus on value, business, or other financial factors • Customer Lens • What I hear from customers • Community Lens • Focus on the relative significance in the community • Engineering Lens • A view focused on differentiating technology, architecture, or technical points
- 12. 12 Docker • Economic Lens •Owned by Docker Inc • $1.3B valuation • Raised $75M from a $1.0B valuation in 2015 • Revenue? • Customer Lens • Confusion around Docker versus Containers (Kleenex Principle) • Early on in investigations • Least sophisticated • Community Lens • Larger/est community • “Docker is dead” • Engineering Lens • Easy installation and setup • Tightly integrated with Docker itself • Not very extensible, and thus quickly outgrown • Valid Use Cases on small node deployments
- 13. 13 Cloud Foundry • EconomicLens • Owned by Pivotal Inc • $2.8B Valuation • Revenue in the ~$270ish Million • Customer Lens • Interested but running into limitations • Attracted to less limiting options • Community Lens • Vibrant/Passionate Community (4,000+ conference attendees) • Controlled by the Cloud Foundry Foundation (a part of the Linux Foundation) • Engineering Lens • Its own datastore is on MySQL • Struggles with persistent applications • A highly structured platform that excels where source code is the deployed artifact Source: http://fortune.com/2017/03/07/pivotal-cloud-foundry-growth/
- 14. 14 Kubernetes • Economic Lens •Controlled by Google Inc. • Who’s making money from Kubernetes (aside from Red Hat)? • Customer Lens • Lots of excitement and interest but… • Confusion and frustration over deployment and day 2 operations • Very much a DIY solution • Community Lens • Headline project to CNCF (a part of the Linux Foundation) • Highly Active (highest growth since the Linux kernel) • Still controlled to a large extent by Google, which leads to less agility • Enormous Buzz and Mindshare (+3500 people at conferences) • Engineering Lens • Best-in-class abstraction model to date • Still young and needs more time to be developed • Huge ecosystem support
- 15. 15 Mesosphere DC/OS • EconomicLens • Maintained by Mesosphere • Rumored $1B Valuation (on $122.25M raised) • Revenue guess is in the $20M • Customer Lens • Customers are very pleased with the platform • Internal pressure from Kubernetes • Highly sophisticated customers with production deployments • Community Lens • Highly technical and more closely knit • Lacking on real community outreach • Engineering Lens • Two-Tier (or application aware) scheduling is truly unique and powerful
- 16. 16 Conclusions, Predictions, andQuestions • Winter is here • Microsoft will buy Docker • Can Kubernetes survive if Google decides to stop funding the project? • Is there room in the market for more than one company/project to live on as a sustainable business?
- 17.
Editor's Notes
- #2 First, a few things about the team that has made this possible. The Dell EMC {code} team is a team made up of open source software engineers and developer advocates, focused on making EMC a well-known name within the open source community. We will focus on one of their projects, REX-Ray, in this presentation.
- #18 First, a few things about the team that has made this possible. The Dell EMC {code} team is a team made up of open source software engineers and developer advocates, focused on making EMC a well-known name within the open source community. We will focus on one of their projects, REX-Ray, in this presentation.