Learn Cloud #

This website is organized as a foundational guide to cloud computing that focuses on understanding concepts, mindsets, and the core principles of the cloud world. The main goal here is not simply to introduce the services of one particular provider, but to build a strong, vendor-neutral cloud mindset.

Cloud computing is often learned backwards: people jump straight into services, dashboards, and technical configuration. As a result, many practitioners know how to use the cloud but don’t necessarily understand why an architecture is designed the way it is, when an approach is the right one, and what its long-term consequences are. This website exists to close that gap.

Why Cloud Fundamentals Matter #

The cloud is not just a “server on the internet”. It combines a business model (pay as you go), an operational model (managed service & shared responsibility), an architectural model (elastic, distributed, failure-aware), and an application development model (cloud-native).

Without a grasp of the fundamentals, using the cloud creates new problems: costs that quietly balloon, fragile architectures that are hard to scale, over-engineering or under-engineering, and excessive dependence on a single vendor. By understanding the basics, we can make rational technical decisions — rather than simply following trends or default recommendations.

Scope of Coverage #

The material on this website is organized progressively following the sidebar TOC, and each topic builds on the others. Every topic is designed to answer the what, why, and when of a cloud concept.

Cloud Computing Overview #

This section covers the big picture of cloud computing before diving into more technical discussions.

• What is Cloud Computing? — The definition of cloud computing, its key characteristics, and a broad view of its ecosystem.
• Cloud Evolution — The journey from mainframes and virtualization to modern, cloud-native computing.
• Problems Solved — The classic pain points of traditional infrastructure that drive cloud adoption.
• Myths and Misconceptions — Common misunderstandings about the cloud that should be cleared up before learning further.

Fundamentals and Core Concepts #

In this section we cover the basic concepts that form the backbone of the cloud. These ideas will keep coming up in other topics, so a solid understanding early on is crucial.

• Shared Responsibility — How security and operational responsibilities are divided between the cloud provider and the user.
• Elasticity vs Scalability — The fundamental difference between elastic capacity and scaling ability, which are often confused.
• Global Infrastructure — Regions, availability zones, and how cloud providers build global infrastructure.
• HA & Fault Tolerance — The difference between high availability and fault tolerance, and how to design failure-resistant systems.
• Control Plane vs Data Plane — The separation of the control path and the data path in modern cloud architectures.

Cloud Service Models #

This website discusses cloud service models conceptually. The focus is not just what’s different, but the architectural, operational, and cost implications of each model.

• IaaS — Infrastructure as a Service: full control over virtual infrastructure with greater operational responsibility.
• FaaS/Serverless — Function as a Service: running code without managing servers, event-driven and pay-per-invocation.
• PaaS — Platform as a Service: abstracting infrastructure so developers can focus on applications, not operations.
• SaaS — Software as a Service: ready-to-use applications fully managed by the provider.
• Choosing a Service Model — A guide to picking the right service model based on context and technical needs.

Deployment Models #

This section explains various cloud deployment patterns, including a realistic discussion of vendor lock-in, operational complexity, and when a model truly makes sense.

• Public Cloud — Provider-managed infrastructure available publicly on a pay-as-you-go basis.
• Multi Cloud — The strategy of using more than one cloud provider at the same time and its implications.
• Private Cloud — Cloud infrastructure dedicated to a single organization, on-premise or hosted.
• Hybrid Cloud — A combination of public and private cloud that are interconnected for flexibility and control.
• Vendor Lock-in — The risk of depending on a single provider and strategies to mitigate it.

Cloud Application Architecture #

These topics cover how to think about designing applications for the cloud. This section is especially important for developers and architects so they don’t carry old patterns into the cloud environment.

• Stateless vs Stateful — The difference between applications that store state and those that don’t, and the implications for scalability.
• Horizontal vs Vertical Scaling — The two scaling approaches and when each one is the right fit.
• Immutable Infrastructure — The principle of replacing infrastructure instead of updating it, for consistency and predictability.
• Event-Driven Architecture — An event-based architectural pattern for decoupling, scalability, and resiliency.
• Twelve-Factor App — The twelve principles for building cloud-native applications that scale easily.

Networking #

This section covers connectivity and network security in the cloud from a conceptual standpoint, not just service configuration.

• Virtual Network (VPC / VNet) — An isolated virtual network as the foundation of connectivity in the cloud.
• Subnet, CIDR, Routing — Network segmentation, IP addressing, and routing in a cloud network.
• Public vs Private Network — When resources should be publicly accessible and when they must stay isolated.
• NAT, Firewall, Security Group — Network protection components and access control at the network level.
• Load Balancing — Distributing traffic across multiple instances for better availability and performance.

Storage #

This section covers the different types of cloud storage along with the trade-offs between performance, availability, and durability.

• Object Storage — Object-based storage that is highly durable, scalable, and ideal for unstructured data.
• Block Storage — High-speed block-based storage attached directly to compute instances.
• File Storage — File-system-based storage that can be mounted and accessed concurrently.
• Durability vs Availability — The difference between data resilience against corruption and data availability when accessed.
• Lifecycle & Data Tiering — Strategies for moving data to cheaper storage tiers based on access frequency.

Compute #

This section covers compute options in the cloud — from virtual machines to managed compute — along with cost and capacity efficiency strategies.

• Virtual Machine — A virtualization-based compute unit with full control over the OS and configuration.
• Container — A lightweight compute unit based on process isolation that is portable and resource-efficient.
• Managed Compute — Managed compute services like App Engine and Fargate that hide infrastructure complexity.
• Autoscaling — The mechanism for automatically adjusting compute capacity based on actual load.
• Spot/Preemptible Instance — Cheaper instances that the provider can terminate at any time.

Security and Identity #

Security in the cloud takes a different approach than traditional infrastructure. This section builds security by design — not security as an afterthought.

• IAM — Identity and Access Management: the system for managing identities and access rights in the cloud.
• Least Privilege — The principle of granting only the minimum access needed to prevent excessive exposure.
• Authentication vs Authorization — The difference between verifying identity and granting permission, and how they’re implemented in the cloud.
• Secret Management — Managing credentials, API keys, and sensitive data securely in cloud environments.
• Zero Trust — A security model that trusts no one by default, whether inside or outside the network.

Observability and Operations #

The cloud demands new ways of monitoring and operating systems. This section emphasizes that failure is expected — and systems must be designed to handle it.

• Logging — Collecting, storing, and analyzing logs from cloud applications and infrastructure.
• Metrics — Quantitative measurement of system health for monitoring and capacity planning.
• Tracing — Tracking a request’s journey across services in distributed systems.
• Alerting — Strategies and configuration for proactively notifying about abnormal conditions.
• Observability vs Monitoring — The difference between the modern observability philosophy and traditional monitoring.

Cost, Billing, and FinOps #

One of the cloud’s biggest differentiators is its cost model. This section covers how to control costs without sacrificing reliability.

• Cloud Pricing Model — How cloud providers calculate and bill for service usage.
• Cost Allocation & Tagging — Strategies for allocating and tracking cloud costs to teams, projects, or products.
• Reserved & Savings Plans — Long-term usage commitments that earn significant discounts.
• FinOps — The practice and culture of collaboratively managing cloud costs between finance, engineering, and business.
• Cost Optimization — Concrete techniques for reducing waste and optimizing cloud spending.

Who This Website Is For #

This website is for developers who want to understand the cloud thoroughly, system engineers and DevOps professionals, cloud architects, students or self-learners, and anyone who wants to build a strong cloud foundation. No deep prior experience is required, but curiosity and a willingness to understand concepts will take you far.

Closing Thoughts #

The cloud is an incredibly powerful tool, but without proper understanding, it can become a source of new complexity. Through this website, we’re invited to understand the cloud from its roots — not just how to use it, but how to think, design, and make wise decisions in the cloud world.

Happy learning, and enjoy exploring the world of cloud computing.

• 11 subject domains — from overview to cost management, arranged systematically according to the sidebar TOC.
• Start with the Overview — clear up cloud misconceptions before diving into deeper technical concepts.
• Core concepts first — shared responsibility, elasticity, HA, and global infrastructure are the foundations that appear in every other topic.
• The service model shapes the architecture — the choice between IaaS, PaaS, FaaS, and SaaS has major implications for design, operations, and cost.
• Networking and security from day one — VPC, IAM, and least privilege are not afterthoughts; design them before deploying any resource.
• Observability is a must — in distributed systems, good logging, metrics, and tracing are prerequisites for operating the cloud with confidence.
• Cost is a technical discipline — understand the pricing model and adopt FinOps early, before the bill becomes a surprise.