Skip to main content

Cloud Foundations

Every major cloud platform—AWS, Azure, and Google Cloud—shares a common set of architectural principles and operational concepts. This section is your entry point to those foundational ideas. It focuses on the vendor-neutral knowledge you need before you ever open a cloud console.

Understanding these concepts will make learning any specific platform faster and more intuitive. You will be able to recognise the common building blocks behind different service names, reason about resilience and scalability without being tied to one provider, and communicate effectively with architects and engineers across teams.

Why Cloud Foundations Matter​

Cloud platforms evolve quickly. Services are renamed, new features are added, and consoles change. The underlying concepts, however, remain stable. The difference between a region and an availability zone, the meaning of a recovery point objective, the trade-offs between horizontal and vertical scaling—these ideas persist.

When you build your mental model on these foundations, you gain a durable skill set. You spend less time memorising product names and more time solving real problems. You can evaluate trade-offs, design resilient systems, and pick up any cloud provider’s documentation with confidence.

This section also prepares you for more advanced topics. Cloud-native architecture, Kubernetes, Infrastructure as Code, and observability all rely on a solid understanding of the core concepts covered here.

What You’ll Learn​

The content is organised into several core domains. Each group covers a set of related ideas that together form a complete picture of modern cloud computing.

Cloud Fundamentals​

  • Cloud Computing Fundamentals – The essential characteristics, benefits, and economic model that define cloud computing.
  • Cloud Service Models – IaaS, PaaS, and SaaS, and the responsibilities each model shifts between you and the provider.
  • Cloud Deployment Models – Public, private, hybrid, and multi‑cloud strategies for how organisations adopt cloud.

Global Infrastructure​

  • Regions – Large geographic areas that contain multiple, isolated data centre locations.
  • Availability Zones – Physically separate sites within a region, engineered for independent failure.
  • Edge Locations – Points of presence placed close to users to reduce latency for content delivery and traffic routing.
  • Fault Domains – Groups of resources that share a common failure point, such as a rack or power bus.
  • Update Domains – Groups of resources that are patched or rebooted together during planned maintenance.

Reliability & Resilience​

  • High Availability – Designing systems that stay operational even when individual components fail.
  • Fault Tolerance – The ability of a system to continue without any interruption when a failure occurs.
  • Disaster Recovery – Processes and architectural patterns for recovering from large‑scale, region‑wide outages.
  • Recovery Point Objective (RPO) – The maximum amount of data loss your business can accept, measured in time.
  • Recovery Time Objective (RTO) – The maximum acceptable time to restore a service after a disruption.

Scalability​

  • Scalability – The capability of a system to handle growing amounts of work by adding resources.
  • Elasticity – The ability to dynamically provision and de‑provision resources to match current demand.
  • Horizontal vs Vertical Scaling – The difference between adding more instances (scale out) and increasing the size of an instance (scale up).

Modern Cloud Architecture​

  • Cloud‑Native Architecture – Designing applications specifically to exploit cloud characteristics like elasticity, resilience, and self‑service.
  • Containers – Lightweight, portable packages that bundle an application with its dependencies.
  • Kubernetes – The industry‑standard platform for orchestrating containers at scale.
  • Serverless Computing – Executing code without managing underlying servers, paying only for actual resource consumption.

Cloud Engineering​

  • Infrastructure as Code (IaC) – Managing and provisioning infrastructure through declarative configuration files.
  • DevOps – A culture and set of practices that unify software development and IT operations to improve delivery speed and reliability.
  • Observability – The practice of instrumenting systems to understand their internal state through metrics, logs, and traces.
  • Cloud Governance – Policies, processes, and controls that ensure security, compliance, and cost management across cloud environments.
  • Cloud Migration – Strategies for moving existing workloads, data, and applications to the cloud.

Cloud Security​

  • Shared Responsibility Model – The division of security obligations between the cloud provider and the customer.
  • Cloud Security Fundamentals – Core principles including identity management, encryption, network protection, and data security in cloud environments.

If you are new to cloud foundations, begin with these core articles:

  1. What is Cloud Computing
  2. Cloud Service Models
  3. Cloud Deployment Models
  4. What is Regions
  5. What is Availability Zones

After these, move into reliability and scalability topics to understand how cloud architectures stay available under load. Then explore modern architecture patterns and cloud engineering practices to complete your foundation.

How Cloud Foundations Connect to Cloud Platforms​

Every concept in this section maps directly to the major cloud providers. A region in AWS is conceptually the same as a region in Azure or Google Cloud—it is a boundary for latency, data residency, and service availability. Availability Zones exist across all three platforms; once you understand their role in high availability, you can design resilient applications regardless of the provider.

Serverless services like AWS Lambda, Azure Functions, and Google Cloud Functions differ in detail but share the same execution model. Containers and Kubernetes operate under the same principles whether you use Amazon EKS, Azure Kubernetes Service, or Google Kubernetes Engine.

When you later explore the provider‑specific sections of this site, you will recognise these patterns immediately. You will not need to relearn the “what” and “why”—only the “how” for each platform.

  • Amazon AWS – See how foundational concepts are expressed in AWS services and architecture.
  • Microsoft Azure – Learn how Azure implements the same principles with its own service model.
  • Google Cloud – Understand how Google’s infrastructure maps onto these universal concepts.

Continue Learning​

After building a strong foundation, deepen your knowledge by exploring provider‑specific material or diving into specialised resources.

  • Amazon AWS – Provider‑specific guides covering compute, storage, networking, and AI services on AWS.
  • Microsoft Azure – In‑depth content on Azure’s management, governance, and hybrid cloud capabilities.
  • Google Cloud – Articles on Google Cloud’s strengths in data analytics, machine learning, and global networking.
  • Cloud Resources – Curated references, glossaries, and links to further learning materials.