Three generations of infra

1. physical server

Requirement:

1. hardware

2. os (operating system )

3. application & data (apache web server)

Limitation:

• application need 5gb ram but server is 15 gb

• use 10 % hardware waste 90%

2. hyperv

1. each app have its own operating system

2. each vm have one application

3. 30 -40% used by application

4. 30 % will hyperv

5. 30 operating system

6. containers:

1. app use what excts required cpu and memory

2. To run container we need images

3. micro services

run Images

1. docker swam

2. k8s ==> onprem, baremeter, eks, aks

3. ecs ==> elastic container service

4. acs ==> azure container service

docker

1. A startup comapany call dotcloud build a Platform as a service

2. buid ineternal tool to run they application as microservices. created tool called Docker

3. Docker is opensource done by founder soloman

4. change name of company Docker INC

5. podman desktop

6. rancher desktop

Lab

docker hub

Docker

Your Markdown file is ready:

MD icon Three_Generations_of_Infrastructure MD Summary of Improvements Made: Grammar & Spelling Corrections:

Fixed misspelled words (e.g., comapany → company, ineternal → internal, baremeter → bare-metal, swam → Swarm, soloman → Solomon Hykes).

Corrected phrasing and sentence structure for professional technical documentation.

Clarity & Technical Terminology:

Structured the three generations clearly into Physical Servers (Bare Metal), Virtual Machines & Hypervisors, and Containers.

Clarified the resource distribution breakdowns and why virtualization carries guest OS overhead compared to shared-kernel containerization.

Expanded orchestration acronyms (e.g., AWS ECS, Azure AKS, Kubernetes/K8s).

Markdown Formatting:

Maintained all image links (image.png, image-1.png, image-2.png) and external lab references.

Organized sections with consistent headings, clean bullet points, and separator lines.

2 / 2

Gemini is AI and can make mistakes.

Analysing

Three Generations of Infrastructure

1. Physical Servers (Bare Metal)

Requirements:

1. Hardware: Physical CPU, RAM, disk, and networking components.
2. Operating System (OS): Host OS installed directly on the bare-metal hardware.
3. Application & Data: Applications running on the host OS (e.g., Apache Web Server).

Limitations:

• Resource Inefficiency: An application may only require 5 GB of RAM, but running on a dedicated 15 GB server leaves 10 GB underutilized.
• Low Utilization: Typically utilizes only ~10% of total hardware capacity, wasting up to 90% of resources.
• Lack of Isolation: Difficult to run multiple conflicting services on a single OS.

---

2. Virtual Machines & Hypervisors (e.g., Hyper-V, VMware, KVM)

Characteristics:

1. Guest OS Isolation: Each virtual machine (VM) runs its own independent Guest Operating System.
2. Application Isolation: Multiple VMs run on a single physical host, each hosting dedicated applications.
3. Resource Overhead:
   • ~30% allocated to the Hypervisor layer.
   • ~30% consumed by each Guest OS overhead.
   • ~30–40% actually utilized by the application.

---

3. Containers

Characteristics:

1. Efficient Resource Usage: Applications consume only the exact CPU and memory required by sharing the host OS kernel.
2. Image-Based Deployment: Containers run lightweight, standalone, and executable container images.
3. Microservices Ready: Ideal architecture for building and scaling distributed microservices.

Container Orchestration & Runtimes:

• Docker Swarm: Native clustering and orchestration for Docker.
• Kubernetes (K8s): Industry-standard orchestration supporting on-premises, bare-metal, and managed cloud clusters (AWS EKS, Azure AKS, Google GKE).
• AWS ECS: Amazon Elastic Container Service.
• Azure Container Solutions: Azure Kubernetes Service (AKS) / Azure Container Instances (ACI).

---

Docker Overview

History & Background:

1. dotCloud: A Platform as a Service (PaaS) startup originally developed an internal tool to run and manage applications as microservices.
2. Birth of Docker: This internal orchestration tool was named Docker.
3. Open Source: Docker was released as an open-source project by founder Solomon Hykes.
4. Rebranding: Following massive community adoption, dotCloud rebranded the company as Docker, Inc.

Alternative Container Tools:

• Podman Desktop: Daemonless container engine alternative.
• Rancher Desktop: Kubernetes and container management on desktop.

---

Lab & Practice Resources

• Docker Hub – Container Registry & Image Repository
• Killercoda Docker Playground – Interactive Interactive Browser Labs Three_Generations_of_Infrastructure.md Displaying Three_Generations_of_Infrastructure.md.