Cloud Architecture Foundations
Cloud architecture becomes easier to learn when you begin with responsibilities and boundaries rather than a provider's catalog. This part establishes the operating model that the rest of the guide uses.
What You Will Learn
By the end of this part, you should be able to:
Describe the responsibilities present in any serious cloud design.
Explain how service models shift work between provider and customer.
Reason about geography, failure boundaries, ownership, and governance.
Translate these ideas across AWS and Azure without relying on one-to-one service mapping.
Chapters
Cloud Responsibilities Before Cloud Services
Build a provider-neutral vocabulary for the responsibilities every cloud design must cover.Shared Responsibility, Control Planes, and Data Planes
See how service choices move operational responsibility without removing customer accountability.Regions, Zones, Edge, and Availability Thinking
Connect workload placement to latency, residency, availability, recovery, cost, and complexity.Resource Hierarchy, Ownership, and Governance
Understand where access, policy, billing, ownership, guardrails, and evidence live.
How the Chapters Connect
The part begins with the responsibilities that transfer across platforms. It then shows how managed services redistribute those responsibilities, places them on real infrastructure and failure boundaries, and finally explains how organizations assign ownership and control. Together, the chapters form the foundation for every capability decision that follows.