Charting Stacks

Container Trends: Plans, Orchestration and CI – A Dataset from Bitnami

Share via Twitter Share via Facebook Share via Linkedin Share via Reddit

Over the last week we have had the opportunity to work with a large set of data collected by Bitnami (full disclosure: Bitnami is a RedMonk client). Bitnami collected this data by means of a user survey across their entire user base, and the survey garnered over 5,000 responses from a request sent to Bitnami’s e-mail distribution list of over 850K. With any data set of this nature, it is important to state that survey results strictly reflect the members of the Bitnami e-mail distribution list.

The data set covered areas including container usage and plans, orchestration tools where containers were being used, CI tools and database choices. For this post we will be focusing on the data around containers and CI.

What makes this data very interesting is the number of companies who are actively using and evaluating containers versus those that are not. One of the issues with many surveys of container users is the automatic bias inherent in the selection criteria. While this data does not eliminate this bias, it does provide some interesting counter balances.

The Population

The overall population breaks out with just over 30% individual developers and the remainder as employees in companies of varying sizes. For the purposes of this analysis we will ignore individual participants, and focus on four sets of users, looking first at those using or planning to use containers.

  • Companies between 2 and 50 employees
  • Companies between 50 and 250 employees
  • Companies between 250 and 1000 employees
  • Companies with over 1000 employees

Container  Usage and Plans?
bitnami-all-usage-c

The first interesting stat that jumped out is the number of participants who stated they are using containers currently, and those that are planning to use containers in the future, and are currently evaluating and developing a container strategy.

We next looked at a breakdown of container usage plans by company size

bitnami-container-plans-company-size

CI Usage Across All Participants

We also looked at the level of CI Usage across all participants

bitnami-ci-all-c

What sticks out here is how many participants are either on manual build processes or have no CI process at all in place. We have commented previously as to just how important CI is as part of the cloud native journey, and for most people looking to use containers at scale CI is where they will need to start.

For those that are using CI, Jenkins, unsurprisingly, comes out with a strong lead.

bitnami-ci-systems-all

Deep Dive – Orchestration Tools

Among those using or planning to use containers we next looked at the types of deployments they currently have.

bitnami-orch-tools-all-container-users-c

As one would expect at this stage of the adoption cycle test/dev far outweighs everything else, with the those running orchestration for less than 50 nodes coming next.

Diving deeper into the orchestration tools, we looked at the orchestration tools organisations of different sizes were looking at.

bitnami-orch-tools-by-cs

Kubernetes was the overall leader here, but a large number of participants are using Docker Swarm. Mesos continues to have a strong foothold as well.

We next looked at the breakdown of how each orchestration tool was being used across each size of enterprise.

Docker Swarm

bitnami-swarm-orchapproach-by-cs-uc

Kubernetes

bitnami-kube-orchapproach-by-cs-uc

Mesos

bitnami-mesos-orchapproach-by-cs-uc

Nomad

bitnami-nomad-orchapproach-by-cs-uc

Reflecting our earlier findings, test/dev is the predominant workload across all company sizes.

CI Approaches of Container Users

bitnami-ci-approaches-by-cs-uc

 

Once again the level of manual deployment, be it either with a CI system or as a completely manual approach was very surprising, looking further into this data, we did a breakdown across the main orchestration tools, and looked at which CI tools participants are using in conjunction with the various orchestration tools.

Docker Swarm

bitnami-swarm-ci-by-cs-uc

Kubernetes

bitnami-kube-ci-by-cs-uc

Mesos

bitnami-mesos-ci-by-cs-uc

Nomad

bitnami-nomad-ci-by-cs-uc

 

Conclusions

A number of trends come through very clearly in the data from the Bitnami survey. Firstly companies still have a journey to go on using CI and CD. In our opinion this is absolutely critical for cloud native applications.

Secondly Docker Swarm has a much stronger presence in the orchestration tools space within this survey population than many commentators believed.  Given that this was in advance of yesterdays announcements around Docker 1.12 and Swarm we would expect to see significantly more competition in this space.

Finally the scale of deployments from the respondents to this survey is still relatively low, with very few companies having over 200 nodes in production. We do expect to see this change over the coming year.

Disclaimers: Bitnami, Docker, Atlassian (makers of Bamboo) are current RedMonk clients.

5 comments

  1. […] Container Trends: Plans, Orchestration and CI – A Dataset from Bitnami […]

  2. […] Container Trends: Plans, Orchestration and CI – A Dataset from Bitnami […]

  3. […] Container Trends: Plans, Orchestration and CI – A Dataset from Bitnami […]

  4. […] Container Trends: Plans, Orchestration and CI – A Dataset from Bitnami […]

  5. […]  Container Trends: Plans, Orchestration and CI – A Dataset from Bitnami […]

Leave a Reply

Your email address will not be published.