Over a million developers have joined DZone.

DZone Research: Container Change

DZone 's Guide to

DZone Research: Container Change

The most dramatic change in the orchestration and deployment of containers has been the growth and adoption of Kubernetes (K8s).

· Cloud Zone ·
Free Resource

To gather insights on the current and future state of containers, we talked to executives from 26 companies. We asked, "How has the orchestration and deployment of containers changed in the past year or so?" Here's what they told us:


  • Definitely, prior to the Docker announcement of adding support for K8s into their EE product, there was still a battle of the orchestrators, between K8s and Swarm. Now that Docker has begun introducing K8s support into EE, there is a lot more clarity on when/where to use each orchestrator for maximum efficiency. You will see a recent tweet from Kelsey Hightower (K8s dev advocate @kelseyhightower) who clearly states that K8s is not recommended for stateful services, yet Docker Swarm is marketed squarely at that use case. Before you would need to know and make a choice, now with Docker EE you can have both. 
  • Customers are talking about deploying in production versus just developing and testing. Containers have high availability and protection. The growth of K8s and a desire to move to production. 
  • The rate at which container solutions are being adopted – Docker for containers and Kubernetes for orchestration. We’re only 25 to 35% up the growth curve. We will not reach the peak for another three years. The cost of owning your own data center is high. 
  • Easier, more documentation, more maturity, better tooling. We're able to set up K8s in five to 10 minutes versus days or weeks. More big companies going open source like Netflix and Google. 
  • Steady evolution with a big moment in CNCF driving cloud computing with K8s is great. We don’t need to stuff everything into it, just run the apps at scale reliably. Prometheus handles the monitoring challenges. There’s enough competition to produce good solutions. A year ago, we had K8s, Swarm, and Mesos. K8s is the clear winner because it’s the most resilient and is able to keep apps running.
  • 1) K8s has matured and gained mindshare, features, and maturity. 2) Quality integrations with open service broker concept. 3) Mesosphere, CloudFoundry, and Docker support K8s. Azure has a service broker. We provide a service broker on-prem. 
  • K8s came out and emerged with broad adoption as the standard for facilitated ecosystems that everyone is supporting. Docker made it a standard. CNCF standards body came up with the K8s standard certified platform in November 2017. Having standards and knowing who’s behind them is huge. This eliminates fragmentation. 
  • Gradual adoption as companies explore and learn the requirement for orchestration technology to move from dev/test to production. Greater adoption into the mainstream – high availability and low latency. Move towards choosing an orchestrator. People were confused what to use but over the last month, K8s has been the winner and now people are learning how to use properly
  • Docker exploded the market and now everything has consolidated behind K8s APIs which provides a level of clarity. Docker is bringing APIs to the desktop. Pivotal realized K8s is good for stateful applications and Cloud Foundry is good for stateless.
  • K8s has emerged as the victor in container management. We started on Docker Swarm and moved.
  • The container ecosystem has been one of the fastest growing communities in the past year. Obviously, last year Kubernetes became the most popular orchestration tool that is supported by all major platforms and cloud providers. This has given enterprises the confidence to move forward with their deployment plans. On the security side, the production deployment of containers, especially public facing ones, are attracting hackers to target container deployments with weak security. 
  • We originally began with Mesos but switched to Kubernetes because we saw the community accelerating so much faster. 
  • The evolution of persistent storage and persistent stateful data within containers. Standardizing on K8s and open source is good for the industry because you’re able to establish best practices, playbooks, and run guides. 
  • The actual orchestration on Kubernetes has been remarkably stable for a few years now. Though one big change has been the move towards Service Meshes like Istio — while not quite related to orchestration directly, it does affect how services communicate — to perform things like load balancing, automatic retry of requests, circuit breakers, tracing — behind a standard "backplane" like the rest of Kubernetes.
  • More evolutionary but K8s becoming widely adopted. The rise of Docker. A combination of solutions is becoming blessed but best practices have not evolved yet.
  • Ramped fairly quickly. K8s is the clear winner in orchestration.
  • K8s and Open Shift and other container orchestration platforms, like Google Container Engine and Amazon’s version, are proliferating. We enable clients to use whatever they like. They are using containers to deploy and standup, take down, and move from place to place daily or hourly taking advantage of spot rates for cloud storage with a promise of up to 80% savings.
  • The most significant recent changes have been the widespread adoption of Kubernetes. With the industry settling on a standard for running containers, it means we can optimize our efforts to the most widely-used technology. This focus also means a greater deal of standardization in the industry and more incentive for bigger players (e.g. Amazon, Microsoft) to invest in the platform.
  • K8s rise in the past year has been incredible. It clears the way for a lot of integration. Open to running containers. Assist with microservices. K8s makes it easy to do. Make container infrastructure more mature and many people are seeing it as a platform.

Everything Else

  • The ease and reliability of deploying the player are amazing. Someone who has never used containers before can now be up-and-running with something distributed in container form in minutes. Basically, it’s becoming a real option for distributing mainstream enterprise software (as opposed to just being a sysadmin's tool).
  • The container orchestration war was settled and that has helped us move beyond evaluating technology to accelerating the process and getting to advanced concepts of which there are a lot to grasp.
  • Growth in container adoption. Now running production on containers. Still a lot of unresolved problems.
  • There has been an exponential progression adoption of containers.
  • At first, deployments were done manually. We would build images in Jenkins or on local desktops and then push them to a repository only to follow that up by logging into Docker Cloud to deploy the updated images. Now we have automated that entire process using Jenkins and APIs to perform every task from building release Docker images, to pushing, editing Docker tags, and redeploying containers.

Here’s who we spoke to:

containers ,containerization ,interview ,kubenetes ,cloud ,k8s ,docker

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}