Containerization
Containerization is a software deployment process that bundles an application’s =code= with all the files(dependencies) and =libraries= it needs to run on any infrastructure
Traditionally, to run any application on your computer, you had to install the version that matched your machine’s operating system. For example, you needed to install the Windows version of a software package on a Windows machine.
Containerization is the packaging of software code with just the operating system (OS) libraries and dependencies required to run the code, to create a single lightweight executable—called a container—that runs consistently on any infrastructure.
https://www.ibm.com/think/topics/containerization
However, with containerization, you can create a single software package, or container, that runs on all types of devices and operating systems.
https://aws.amazon.com/what-is/containerization/
Container
https://www.ibm.com/think/topics/containers
https://www.docker.com/resources/what-container/
A container is a standard unit of software that packages up code and all its dependencies so the application runs quickly and reliably from one computing environment to another.
Isolated
Containerized applications are “isolated,” meaning they do not bundle in a copy of the operating system. Instead, an open-source container runtime or container engine (like Docker runtime engine) is installed on the host’s operating system and becomes the conduit for containers to share an operating system with other containers on the same computing system.
container engine
benefit
Container Engine
Others
containers, enabling us to run multiple applications in isolation on a single virtual server. Containers provided the benefit of creating applications once and deploying them anywhere. However, the challenge of managing, patching, and securing the underlying servers persisted.