Traditional Deployment VS Virtualization VS Container

History of running a software Traditional Deployment

• Early on, organizations ran applications on physical servers.
• Install or use an existing operating system.
• Install the tools needed by your software.
• Install dependencies of your software.
• Run your software.

Issues with traditional deployment

• Isolation issue, no way to define resource boundaries for applications in a physical server, and this caused resource allocation issues.
• Scaling issues as resources were underutilized.
• It was expensive for organizations to maintain many physical servers.

Virtual Machines! How is virtualization possible?

• Virtualizing hardware produces virtual machines (VMs).
• Virtualization allows you to run multiple VMs on a single physical server. Each VM includes a full copy of an operating system, the application, necessary binaries, and libraries - taking up tens of GBs.
• Virtualization allows more effortless adding and updating of applications that solve the scalability issue.
• Virtualization allows better utilization of resources.
• Virtualization isolates applications between VMs.

Containers! What is a Container?

• The process of virtualizing the operating system produces containers.
• A container is a virtual operating system.
• A container is an abstraction at the OS layer that packages code and dependencies together as a standardized unit of software.
• Containers take up less space than VMs, boots quickly, and in isolation.
• Containerization eliminates infrastructure wasted resources and utilizes them.