IS THE STANDARD FOR CONTAINER ORCHESTRATION

No matter the data source, Kubernetes is the clear leader in cloud-native orchestration platforms among CIOs, operations and developers alike. As has been learned from past vendor efforts to do so, no one can buy the network effect. All the data points to Kubernetes and containers (, rkt) as having this network effect. Kubernetes’ momentum, market maturity and usage is not matched by any comparable solution as the data of its first year in general availability (captured below) makes clear.

In One Year

779 Kubernetes Jobs 7,110 Kubernetes News Articles 4,635 Kubernetes Professionals

GITHUB

32,113 140 825 COMMITS RELEASES CONTRIBUTORS

TOP 100 TOP 2 TOP .01% FORKED GITHUB PROJECT STARRED GO PROJECT STARRED GITHUB PROJECT

WEB SEARCH INTEREST

JUN 2015 SEP 2015 DEC 2015 MAR 2016 JUN 2016

KUBERNETES CLOUDFOUNDRY DOCKER SWARM

How Organizations Leverage Kubernetes

Component for self-service distributed cloud platform Container hosting and orchestration that is managed - i.e. a DIY enterprise PaaS by operations (not self-service)

Hosting of off-the-shelf applications and frameworks Multicloud orchestration supported by Kubernetes

KUBERNETES MESOS/MARATHON DOCKER SWARM CLOUD FOUNDRY

Cloud Native Computing Apache None Cloud Foundry Foundation FOUNDATION Foundation (part of Linux Foundation)

Apprenda (Kismatic), CoreOS Mesosphere (DCOS) Docker Inc (Swarm) Pivotal (PCF), HPE (Helion) SOFTWARE (Tectonic), Engine Yard (Deis), Red VENDORS Hat (OpenShift)*, Mesosphere (PRODUCT (DCOS)*, (Rancher)* NAME) *Kubernetes is a component of a larger product

PUBLIC CLOUD Google Container Engine, Red Hat A number of public cloud providers, Azure IBM, Predix (GE's IoT PaaS) SERVICE OpenShift, and many more currently including Azure, use Mesos as part of PROVIDERS in development. its underling architecture.

• Component for self-service • Component for self-service • Component for self-service • Off-the-shelf self-service distributed cloud platform - i.e. a distributed cloud platform - i.e. a distributed cloud platform - i.e. a distributed cloud platform DIY enterprise PaaS DIY enterprise PaaS DIY enterprise PaaS • Multicloud orchestration • Container hosting and • Container hosting and • Container hosting and orchestration that is managed by orchestration that is managed by orchestration that is managed by USE-CASES operations (not self-service) operations (not self-service) operations (not self-service)

• Multicloud orchestration • Multicloud orchestration • Multicloud orchestration

• Hosting of off-the-shelf • To host Big Data (Spark) • Host applications and frameworks applications and frameworks frameworks that were purpose specifically built for Docker Swarm supported by Kubernetes built for Mesos

YEARS 1+ 7+ 1+ 5+ RELEASED

• Extremely large and diverse Mesos has a community of a few Most of the Swarm contributions Most of the Cloud Foundry vendors and some key end-users. come from Docker. contributions come from Pivotal • One of the top projects on GitHub Mesosphere, who also sells the and IBM. (0.01% in terms of starred and #1 product, is top contributor. in terms of activity)

• Large Slack and Stackoverflow community for support and COMMUNITY collaboration

• More professionals list Kubernetes on their LinkedIn profiles than any other comparable solution

• Large number of vendors and providers hedges against lock-in

Like Hadoop, Kubernetes was Mesos is productized and sold by Docker Swarm is productized and Cloud Foundry is productized and orginally developed from a project creators of the project, Mesosphere. sold by creators of the project, mostly sold by the creators of the used internally at a large tech Docker. project, Pivotal. HPE also has an company that was open source for installable version of Cloud Foundry other vendors, not associated with but the vast majority of revenue BUSINESS original project, to productize into goes to Pivotal, and HPE has since MODEL commerical software. Google has abandoned its Cloud Foundry-based stated that it has no plans to offer public cloud and invested more a commercially supported and heavily in Kubernetes, which power installable version of Kubernetes. HPE's cloud, and Mesosphere (led $73.5 million Series C round).

• 10 years of Google research and • Used by a few large organizations • Docker owns the current standard • Cloud Foundry has been around development in containers and at massive scale (e.g. Twitter) for containers for a number of years orchestration • Interest from large financial • Docker Inc is immensly popular. • Decent documentation that has • Clear Market Leader: Largest institutions and public cloud Dockercon has over 5K attendees gone through many renditions adoption and interest amongst providers • Mostly controlled by a single • Large practices around Cloud developers and the enterprise • Proven history supporting large vendor who can decide product Foundry have been built by system • By far the largest community number of nodes at Twitter direction integrators actively contributing to projects of • Spark, a Mesos framework, is • Single throat to choke for features • Single throat to choke for features any comparable solution seeing traction in the Big Data and roadmap and roadmap STRENGTHS • Strong number of options for market productized version • Mostly controlled by single vendor • High availability of persistent who can decide product direction storage • Single throat to choke for features • Growing number of service options and roadmap from top public cloud providers

• Large practices from system integrators built around Kubernetes

• Documentation • Mesos strength is in Big Data • Weak pulse on GitHub with • Built on concepts from public and analytics and not container smaller number of contributors PaaS and shares many of the now • No Windows Server support orchestration and commits than other similar outdated, and little used, concepts (active area of development with projects like Buildpacks early 2017 expected release) • Not as much traction among developers • Only available from Docker Inc • Monolithic cloud platform not • No single throat to choke on ideal for DIY projects or those that the OSS project (requires a • Complexity - does too much and • Little traction from developers want best of breed individual tools distribution or active participating) is too generic - needs frameworks • More aimed at developers than for most use cases • Lock-in to single vendor is WEAKNESSES • Most organizations will need central IT strong possibility given Pivotal’s commerically supported • Championed by single vendor • Uses Docker APIs, which means dominance in the market and Kubernetes due to complexity of has compatibility with the Cloud Foundry’s monolithic maintenance and installation container but limits functionality platform where services only work • Kubernetes is a mature solution for enterprise IT use case with other Cloud Foundry services but its relative age and rapid growth means that the Kubernetes version you can get at some future date will have many more features

• Expand to multiple data center / • Mesos frameworks for the Big • Docker containers are popular • Large financial backing by Dell/ multicloud deployments use case- Data market and Docker Inc can use that EMC Foundation and others i.e. the Ubernetes project momentum to drive other projects • Mesos can become a general • Cloud Foundry can disagregate its such as Swarm and newer Swarmkit • Because of the Hadoop business resource management solution for solution and choose best of breed model, Kubernetes is going to COTS and other solutions that • Docker Inc can leverage its brand container orchestration and other be adopted by more vendors and don’t yet work on Kubernetes to land big partnerships and go- solutions providers that will productize and to-market opportunities with large OPPORTUNITIES • Appliance market make new services vendors that can distribute new solutions • Kubernetes momentum and lead can transition into a true de-facto standard in the orchestration space that is similar to Linux in the OSS enterprise operating system market

• Kubernetes uses Docker Inc’s • Kubernetes has become much • Kubernetes and Mesos are • DIY cloud platform projects container format as a default, but more popular than Marathon on currently more popular in the can now be built with best Docker Inc has its own plans for Mesos enterprise of breed services and tools the container orchestration space (Docker containers, Kubernetes • The complexity of maintaining • It is yet to be determined if orchestration, etc.). Pivotal • Kubernetes is relatively complex; Mesos and all its frameworks on a Docker Inc can transition its already sees newer solutions as customers going the DIY route single product means Mesosphere popular brand to tools beyond its a competitive threat may need to seek professional is commiting to a lot and may container services or Kubernetes spread too thin • Monolithic PaaS has become less • Docker Inc has raised a lot of distributions popular with time • Some of Mesosphere’s main funding in a very short period of THREATS • The community has grown backers have already hedged their time and needs to grow into a high • Pivotal Cloud Foundry is often extremely fast and is managing bets by also adopting Swarm and valuation installed as a CTO initiative to a huge mono-repo on GitHub Kubernetes. There is no single “satisfy developers”, but most (something that site was not force, besides Mesosphere, of these developers have never originally designed to do) pushing only Mesos now actually used Cloud Foundry

• Mesos main backer, Mesosphere, has raised a lot of money in a very short period of time and now needs to justify and grow into a high valuation