Scribd
Upload
40 views1 page

History of Containerisation

The document discusses the evolution of computing environments and platforms over time: 1) Traditionally, organizations ran applications on physical servers which caused resource allocation issues and underutilization of resources. 2) Virtualization allowed operating systems to run side by side on a physical server in isolated virtual machines (VMs), improving resource utilization but requiring more resources per application. 3) Containers became popular as they are more lightweight than VMs and allow deploying multiple applications on a single server sharing its operating system kernel.

Uploaded by

Kristian Pacquing
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
40 views1 page

History of Containerisation

The document discusses the evolution of computing environments and platforms over time: 1) Traditionally, organizations ran applications on physical servers which caused resource allocation issues and underutilization of resources. 2) Virtualization allowed operating systems to run side by side on a physical server in isolated virtual machines (VMs), improving resource utilization but requiring more resources per application. 3) Containers became popular as they are more lightweight than VMs and allow deploying multiple applications on a single server sharing its operating system kernel.

Uploaded by

Kristian Pacquing
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

History

The evolution of environments and platforms:

• Traditional deployment era: Organisations ran applications on physical servers.


o There was no way to define resource boundaries for applications in a physical
server, and this caused resource allocation issues.
o A solution for this would be to run each application on a different physical
server. But this did not scale as resources were underutilised, and it was
expensive for organisations to maintain many physical servers.
• Virtualised deployment era: Each VM is a full machine running all the components,
including its own operating system, on top of the virtualised hardware. The hypervisor
enables multiple operating systems to run side-by-side, all with access to the same
physical server resources.
o Virtualisation allows operating systems to be isolated between VMs and
provides a level of security as the information of one application cannot be
freely accessed by another application.
o Virtualisation allows better utilisation of resources in a physical server
because an operating system can be added or updated easily.
o Since each VM image includes an OS and a virtual copy of all the hardware
the OS requires, VMs require more resources (CPU and RAM).
• Containerised deployment era: The container shares the kernel of the host OS with
other containers, and the shared part of the OS is read-only.
o The containers are lightweight, so you can deploy multiple containers on a
single server. In comparison to the VMs, a single node doesn't have to run
multiple OSs at the same time.
o You can simulate different OSs with base layers that provide abstraction and
system call translation for the underlying OS.
o Containers share the same OSs, thus they must run on the same kind of OS.
• Microservices era: Kubernetes (and other container orchestrators) has been designed
with in mind the Microservices architecture.
o It is aligned with Event-Driven architecture and Service-Oriented architecture
principles.
o Although the distributed nature of microservices adds complexity to the
architecture, one of the greatest benefits of microservices is scalability (each
component can be scaled individually) and modularity (components are
loosely coupled and can be maintained independently).
o Migration of old monolith can be done incrementally. The new features are
developed as microservices and, in the meantime, the existing features can be
refactored.
• Cloud era: cloud offers elastic provision of resources and managed services that can
speedup the development of new features.

You might also like