Cloud Computing 13 min read

Overview of Cloud Computing: From Physical Servers to Containers and PaaS

This article provides a comprehensive overview of cloud computing, tracing its evolution from physical servers through virtualization and IaaS/PaaS models to modern container and cloud‑native architectures, and explains key concepts, major vendors, and the challenges of automation and resource pooling.

Architects' Tech Alliance
Architects' Tech Alliance
Architects' Tech Alliance
Overview of Cloud Computing: From Physical Servers to Containers and PaaS

Cloud Computing Overview

Cloud computing addresses four core aspects: compute, network, storage, and applications. Compute refers to CPU and memory, network to connectivity, storage to data persistence, and applications to platform services. The first three correspond to IaaS, while applications correspond to PaaS.

Development Stages

Stage 1 – Consolidation: Physical Devices

In the early Internet era, organizations relied on physical servers (Dell, HP, IBM, Lenovo), hardware switches/routers (Cisco, Huawei), and disks/SSDs. While powerful, physical devices suffer from manual operation, resource waste, and poor isolation.

Manual operation: Installing software, configuring switches, adding disks all require on‑site staff.

Resource waste: Small workloads often consume large‑capacity hardware.

Poor isolation: Multiple applications share the same hardware, leading to contention and failure propagation.

Stage 2 – Separation: Virtualization

Virtualization abstracts physical compute, network, and storage into virtual machines, virtual switches, and virtual storage, solving manual ops, resource waste, and isolation issues. Leading solutions include VMware, Xen, KVM, Open vSwitch, LVM, and Ceph.

However, virtualization still requires manual placement of VMs and network configuration, limiting cluster size and increasing operational overhead.

Stage 3 – Consolidation: Cloud Computing

Cloud computing introduces pooling of resources managed by schedulers, reducing the need for manual Excel tracking. Public cloud providers (AWS, Google Cloud) built on Xen/KVM, while private clouds use OpenStack components Nova (compute), Neutron (network), and Cinder (storage).

Private‑cloud vendors typically sell raw resources and emphasize hardware specifications, whereas public‑cloud vendors focus on application‑friendly services such as databases, load balancers, and caches, forming the PaaS layer.

Stage 4 – Separation: Containers

Containers package applications and their runtime environment into standardized, portable units, enabling rapid deployment across development, testing, and production. Tools such as Docker and orchestration platforms (Kubernetes, Mesos) embody this approach.

PaaS Overview

PaaS abstracts application‑level services, offering ready‑to‑use components (databases, caching, big‑data platforms) and automation tools (Puppet, Chef, Ansible, Cloud Foundry) to achieve elastic scaling without manual configuration.

Challenges remain because environment differences (OS version, user accounts, library paths) can break scripts when moving between data centers or cloud providers.

Author: Liu Chao, Chief Cloud Architecture Engineer at NetEase Cloud, with 10 years of experience in cloud computing, OpenStack, Kubernetes, and related open‑source technologies.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

cloud computingIaaSPaaSOpenStackContainers
Architects' Tech Alliance
Written by

Architects' Tech Alliance

Sharing project experiences, insights into cutting-edge architectures, focusing on cloud computing, microservices, big data, hyper-convergence, storage, data protection, artificial intelligence, industry practices and solutions.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.