Core Cloud Capability Decisions
This part turns the foundation into concrete design choices. The goal is not to memorize categories of services, but to decide where trust, communication, execution, state, contracts, and controls should live.
What You Will Learn
By the end of this part, you should be able to:
Design human and workload trust boundaries.
Choose connectivity, runtime, data, and integration models from requirements.
Explain the operational and security consequences of each choice.
Compare provider implementations without losing the underlying decision model.
Chapters
Identity, Access, and Trust Boundaries — establish principals, authorization, federation, least privilege, and evidence.
Networking, Segmentation, and Private Connectivity — design intentional communication paths and ownership boundaries.
Runtime Selection: VMs, Platforms, Containers, and Functions — balance control, scaling, portability, and operational burden.
Storage, Data, Analytics, and Consistency Choices — match state to access patterns, lifecycle, governance, and recovery needs.
APIs, Messaging, Events, Streams, and Workflows — choose explicit communication and coordination contracts.
Security, Encryption, Detection, and Evidence — compose preventive, detective, responsive, and evidentiary controls.
How the Chapters Connect
Identity defines who and what can act. Networking defines permitted paths. Runtime and data choices place execution and state. Integration makes relationships between systems explicit. Security then tests and protects the complete design rather than sitting beside it as an afterthought.