3.3.2. Cloud Computing Concepts (Models, Characteristics)

💡 First Principle: Cloud computing delivers on-demand IT resources over the internet with pay-as-you-go pricing, characterized by elasticity, self-service, and broad resource pooling.

Scenario: A startup needs to launch a new web application. They don't have the capital to buy their own servers. They decide to use a public cloud provider's IaaS offering to host their application on virtual servers, allowing them to pay only for the resources they use and scale up as their user base grows.

Cloud computing is a model for delivering IT services, not a single technology.

• Cloud Models (Deployment):

  • Public Cloud: Services are offered over the public internet and are available to anyone who wants to purchase them (e.g., AWS, Azure, GCP).
  • Private Cloud: Cloud infrastructure is operated solely for a single organization. Can be on-premises or hosted by a third party.
  • Hybrid Cloud: A combination of public and private clouds, bound together by technology that allows data and applications to be shared between them.
  • Community Cloud: Infrastructure shared by several organizations with common requirements (e.g., agencies or hospitals with the same security and compliance needs). Unlike a private cloud it is not for one organization; unlike a public cloud it is not open to everyone.

• Cloud Models (Service):

  • IaaS (Infrastructure as a Service): The provider offers fundamental resources like virtual machines, storage, and networking. You manage the OS and up. Examples: AWS EC2, Azure Virtual Machines.
  • PaaS (Platform as a Service): The provider manages the platform (including OS). You manage your applications and data. Examples: Heroku, Azure App Service, Google App Engine.
  • SaaS (Software as a Service): The provider manages everything. You just use the software. Examples: Microsoft 365, Google Workspace, Salesforce.
  • DaaS (Desktop as a Service): The provider hosts and manages virtual desktops that users reach over the internet (for example AWS WorkSpaces or Azure Virtual Desktop); it is the cloud-hosted form of the VDI idea in 3.3.1.

• Cloud Characteristics:

  • Elasticity: The ability to automatically scale resources up and down based on demand. Paired with pay-as-you-go billing, capacity follows demand instead of being bought up front; the cloud is not automatically cheaper, and capacity is still limited by account quotas and budget.
  • Shared/Pooled Resources: Resources are shared among multiple customers (multitenancy), also called resource pooling; sharing drives down cost.
  • Metered Utilization: You pay only for what you use (also called measured service).
  • File Synchronization: Services like Dropbox or OneDrive that keep files consistent across multiple devices.
  • On-Demand Self-Service: Users provision resources (e.g., a new virtual server) themselves through a web portal in minutes, with no interaction with the provider's staff.
  • High Availability: Provider redundancy keeps services running through hardware failures.

• Cost, Responsibility & Portability:

  • CapEx to OpEx: Instead of a large upfront capital expense for hardware, the company pays a recurring operating expense (monthly or yearly) for what it uses. Because public providers operate at massive scale (economies of scale), they can offer resources more cheaply than most companies could build them.
  • Shared Responsibility Model: The provider secures the physical data center and underlying infrastructure; the customer secures what it configures (e.g., firewall rules, guest OS, data, access). The split shifts with the service model (IaaS gives the customer the most).
  • Vendor Lock-In: Proprietary high-level provider services make moving to another provider hard; building on open-source technology and containers keeps applications portable.

Typical IaaS migration phases (in order): (1) inventory and assess on-premises workloads, dependencies, and data volumes; (2) design the target cloud architecture (virtual network, instance sizes, storage tiers); (3) pilot-migrate a non-critical workload and validate function and performance; (4) cut over the remaining workloads, decommission on-premises hardware, and optimize cloud costs.

⚠️ Common Pitfall: Underestimating the importance of managing cloud costs. The pay-as-you-go model is a double-edged sword; if resources are not properly managed, costs can spiral out of control.

Key Trade-Offs:

• Control (IaaS) vs. Ease of Use (SaaS): IaaS gives you the most control but also the most responsibility. SaaS is the easiest to use but offers the least control.

Reflection Question: How does the cloud characteristic of "elasticity" provide a significant advantage over traditional on-premises IT for a business with unpredictable or seasonal traffic?