DZone Research: Container Change
DZone Research: Container Change
The most dramatic change in the orchestration and deployment of containers has been the growth and adoption of Kubernetes (K8s).
Join the DZone community and get the full member experience.Join For Free
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.
- 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.
- 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.
- 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:
- Matt Chotin, Sr. Director of Technical Evangelism, AppDynamics
- Jeff Jensen, CTO, Arundo Analytics
- Jaime Ryan, Senior Director, Project Management and Strategy, CA Technologies
- B.G. Goyal, V.P. of Engineering, Cavirin Systems
- Tasha Drew, Product Manager, Chef
- James Strachan, Senior Architect, CloudBees
- Jenks Gibbons, Enterprise Sales Engineer, CloudPassage
- Oj Ngo, CTO and Co-founder, DH2i
- Anders Wallgren, CTO, Electric Cloud
- Navin Ganeshan, Chief Product Officer, Gemini Data
- Carsten Jacobsen, Developer Evangelist, Hyperwallet
- Daniel Berg, Distinguished Engineer Cloud Foundation Services, IBM
- Jack Norris, S.V.P. Data and Applications, MapR
- Fei Huang, CEO, NeuVector
- Ariff Kassam, V.P. Product, NuoDB
- Bob Quillan, V.P. Container Group, Oracle
- Sirish Raghuram, CEO and Co-founder, Platform9
- Neil Cresswell, CEO/CTO, Portainer.io
- Sheng Liang, Co-founder and CEO and Shannon Williams, Co-founder and VP of Sales, Rancher Labs
- Bill Mulligan, Container Success Orchestrator, RiseML
- Martin Loewinger, Director of SaaS Operations and Jonathan Parrilla, DevOps Engineer, SmartBear
- Antony Edwards, CTO, Eggplant
- Ady Degany, CTO, Velostrata
- Paul Dul, V.P. Product Marketing Cloud Native Applications, VMware
- Mattius McLaughlin, Engineering Manager & Containers SME, xMatters
- Roman Shoposhnik, Co-founder, Product & Strategy, Zededa
Opinions expressed by DZone contributors are their own.