Software development in the enterprise is no longer the exclusive domain of technology companies. Organizations across every sector — financial services, healthcare, retail, manufacturing — are investing in custom applications to serve both customers and internal stakeholders. In that environment, the tools and methodologies used to build and ship software matter enormously to the bottom line.
One technology that has gained significant traction is the software container. For CIOs evaluating where to direct engineering investment, understanding what containers actually are, what they genuinely solve, and where they fall short is essential before signing off on a platform migration or a new toolchain budget.
What Is a Software Container?
A container is a lightweight, standalone, executable package that includes everything needed to run a piece of software: the code, runtime, system libraries, and configuration. Unlike traditional virtual machines (VMs), containers share the host operating system kernel rather than running a full OS per instance. This makes them faster to start, cheaper to run at scale, and easier to move between environments.
The practical result is that a containerized application behaves the same way on a developer’s laptop, in a continuous integration pipeline, and in a production cloud environment. That consistency closes one of the most persistent gaps in enterprise software delivery: the “works on my machine” problem.
Why Containers Matter to the Enterprise
According to Jay Lyman, principal analyst at 451 Research (as quoted in a 2017 CIO Dive article), the core enterprise advantages of containers are speed, simplicity, and efficiency — particularly in helping developers move faster, onboard more quickly, and build applications for the cloud. He noted that containers allow organizations to “more simply create and destroy infrastructure and applications as needed.”
Chip Childers, then CTO of Cloud Foundry, framed containers within a broader strategic context: organizations adopting containers see them as part of a larger shift toward continuous delivery, greater agility, and operational flexibility.
Brian Gracely, then director of product strategy at Red Hat, identified several concrete use cases enterprises were already pursuing:
- Modernizing existing legacy applications
- Building new cloud-native applications from scratch
- Accelerating big data pipelines and analytics workloads
- Exploring Internet of Things (IoT) opportunities
The open source ecosystem — including projects like Cloud Foundry, Kubernetes, and Docker — has accelerated the expansion of container use cases significantly, because improvements created by one organization benefit the entire community.
Containers vs. Virtual Machines: Coexistence, Not Replacement
One of the most important things CIOs need to understand is that containers do not yet replace virtual machines in all scenarios. VMs have been in enterprise production for decades and carry a mature ecosystem of tooling, support, compliance frameworks, and operational knowledge.
Containers do not offer full feature parity with VMs in every dimension. Strong VM isolation, mature snapshot and backup tooling, and decades of compliance-ready configurations still give VMs an edge in certain regulated or legacy contexts. Lyman noted that what enterprises should expect is a period of mixed use and coexistence, with containers progressively displacing VMs for specific workload types — not a wholesale replacement.
Containers Are Not Cloud-Dependent
Because containers emerged around the same time many enterprises began cloud migrations, the two technologies are often conflated. This is a common misconception worth correcting explicitly.
As Lyman put it: “Adopting container technology doesn’t have to be dependent on moving from on-premises to cloud infrastructure. There are container platforms out there that allow for deployment on-prem as well as on any cloud, hybrid or public.”
CIOs should evaluate container platforms on their own merits — portability, developer productivity, CI/CD integration — rather than treating container adoption as synonymous with a cloud migration project.
Where to Start: Challenges and Practical Guidance
Many organizations find the entry point for containers unclear. The technology ecosystem around container engines, orchestration platforms, networking, and storage continues to evolve rapidly, which can make it difficult to know where to commit.
Developer-Led Adoption Creates Operational Gaps
In practice, containers are typically adopted first by developers seeking faster build-and-test cycles. Operations teams are then left to address the resulting questions around networking, security, persistent storage, high availability, and compliance. Gracely described this reactive pattern as a source of friction that CIOs should proactively address.
A more effective approach, he argued, is to treat container adoption as a platform discussion — one that brings development and operations together from the start, with a shared focus on accelerating software delivery safely.
Legacy Application Migration Is Hard
Container technology is best suited to greenfield projects. Migrating existing monolithic or tightly coupled applications to containers can be costly and time-consuming. CIOs should be realistic about the effort involved and prioritize new workloads and services as initial container candidates, rather than attempting to lift-and-shift legacy systems wholesale.
Platform Selection
A recurring challenge for enterprises — particularly mid-sized organizations — is that many commercially available container platforms are designed and optimized for massive-scale deployments. CIOs should evaluate whether a given platform fits their actual scale and operational maturity, not just the largest reference customers the vendor promotes.
Containers Are Not a Panacea
Containers are a tool, not a strategy. Childers was direct on this point: “They could be really key in streamlining [software delivery], making it more efficient and eliminating the difference between development and production departments, which frequently is a major problem. But they’re not a panacea. They’re technology that you can use as part of changing the way that your company operates and uses technology.”
CIOs should evaluate containers within the broader context of their software delivery lifecycle — alongside CI/CD pipelines, DevOps culture, infrastructure automation, and observability tooling. Containers accelerate delivery when the surrounding process and culture are ready to support them.
Key Decisions for CIOs Moving Forward
If your organization is considering a container initiative, several practical considerations apply:
- Control costs rigorously. Mark Balch, then VP of product at Diamanti, advised ensuring that both capital and operational expenditure for the container stack — software and underlying infrastructure — are competitive with public cloud equivalents. Traditional enterprise virtualization infrastructure is often too expensive in time, money, and training overhead to simply bolt containers on top of.
- Choose commercially supported platforms. Childers’ advice was unambiguous: do not attempt to build and manage your own container system. “Creating your own platform is extremely difficult and risky and probably not the best use of time for your valuable engineers. Focus your top engineers on the hardest business problem, not the hardest plumbing problems.”
- Start with testing, development, and greenfield workloads. Production adoption for mission-critical applications requires additional investment in security hardening, persistent storage strategies, and operational runbooks. A phased approach reduces risk.
- Plan for organizational change. Container adoption often surfaces cultural and process gaps between development and operations. CIOs should budget for training, workflow redesign, and cross-functional alignment — not just tooling.
The Outlook
Containers have an established and growing role in enterprise software delivery. Adoption has continued to expand since this topic first gained broad executive attention, with Kubernetes now the dominant orchestration platform and container-native tooling maturing across security, networking, and observability. That said, the technology is not universally applicable, and the hype that surrounded early container discourse has given way to a more grounded understanding of where containers genuinely add value.
For CIOs, the right posture is informed pragmatism: understand what containers solve, invest in the platform and people decisions that support them, and integrate them into a broader strategy for continuous delivery and operational efficiency — rather than adopting them as an end in themselves.
This article draws on reporting originally published by CIO Dive in 2017, with quotes from Jay Lyman (451 Research), Chip Childers (Cloud Foundry), Brian Gracely (Red Hat), and Mark Balch (Diamanti).