However, to run containers at enterprise scale is a different proposition than running containers in development: It’s helpful to have an orchestration layer that manages resources, scheduling, load balancing and more. There are many choices for container orchestration. In addition to Kubernetes, other choices include solutions like Docker EE, Azure Kubernetes Services (AKS) and AWS ECS, which all now support Kubernetes.
Docker is an attractive option for many enterprises, as it is lightweight, portable and hardware-agnostic. When it comes to containers, there are two key technologies that you’ve undoubtedly heard a lot about: Docker and Kubernetes.
Operations then creates the framework for running containers, and from there, development teams own the containers. Practically speaking, to deliver this within the DevOps environment, operations teams create the DevOps highway with guardrails and road signs, and development teams are responsible for driving on it. Using our expressway analogy, containers are like tractor trailers that are able to deliver many elements together without consideration for the underlying infrastructure, and in the process, they're able to move each one faster to their destination and with less risk.
By removing the need to tailor code for each and every different system dependency, containerized applications can easily be delivered to service agnostic infrastructure for faster deployment. As I wrote in an earlier column, " DevOps allows us to turn the one-lane road of traditional IT into a broad, paved expressway safe for travelers of every stripe." The application of automation, coupled with guardrails and rules of the road, increases development and operations productivity while removing human-error-induced risk from the system.Ĭontainers build on these DevOps benefits.