Executive Summary
Every cloud platform is built from a common set of architectural building blocks. While AWS, Azure, Google Cloud, Oracle Cloud Infrastructure (OCI), and IBM Cloud use different service names, they all provide similar capabilities for running applications, storing data, connecting resources, securing environments, and automating operations.
Understanding these building blocks is one of the most important milestones in a cloud engineer’s journey. It shifts your thinking from memorizing provider-specific services to understanding the underlying architecture patterns that exist across all cloud platforms.
In this lesson, you will learn the core building blocks of cloud computing, how they appear across the major cloud providers, and how they combine to create modern multi-cloud architectures.
Introduction: Why Cloud Building Blocks Matter
In the previous lesson, The Five Major Cloud Providers: AWS, Azure, Google Cloud, OCI and IBM Cloud Compared, we learned that cloud providers offer hundreds of services.
For beginners, this can feel overwhelming.
AWS alone offers more than 200 services. Azure, Google Cloud, OCI, and IBM Cloud provide similarly large portfolios. Trying to learn every service individually is not practical.
Fortunately, most cloud services can be grouped into a small set of common architectural building blocks.
Whether you deploy an application in AWS, Azure, Google Cloud, OCI, or IBM Cloud, you will eventually work with the same fundamental concepts:
- Compute
- Storage
- Networking
- Identity
- Security
- Databases
- Observability
- Automation
The figure below illustrates the foundational building blocks that exist across all major cloud platforms.
Learning Objectives
By the end of this lesson, you will be able to:
- Explain the core building blocks of cloud computing.
- Understand how cloud services are grouped into common architectural categories.
- Recognize equivalent building blocks across AWS, Azure, Google Cloud, OCI, and IBM Cloud.
- Understand how cloud applications use multiple building blocks together.
- Explain how multi-cloud architectures are constructed from common cloud building blocks.
What Are Cloud Building Blocks?
Cloud building blocks are the foundational services that cloud providers use to create larger solutions.
Think of them as digital Lego pieces.
Individual building blocks provide specific capabilities such as running applications, storing data, securing access, or connecting networks. By combining these blocks, organizations can build everything from simple websites to large-scale enterprise platforms.
The figure below shows how a typical cloud application relies on multiple building blocks working together.
The Eight Core Building Blocks of Cloud Computing
Compute
What It Does
Compute is the building block responsible for running workloads.
Every application, website, API, database, AI model, or container eventually requires compute resources to execute instructions.
Without compute, applications cannot run.
Examples include:
- Virtual machines
- Containers
- Kubernetes clusters
- Serverless functions
- GPU workloads
The figure below shows where compute fits within a typical cloud workload.
Engineer Perspective
Cloud engineers use compute services to deploy applications, APIs, containers, and automation workloads.
Architect Perspective
Architects determine which compute model is most appropriate:
- Virtual Machines
- Containers
- Kubernetes
- Serverless
- AI Accelerators and GPUs
The decision affects scalability, operations, cost, security, and resilience.
Storage
What It Does
Storage is responsible for persisting data.
Applications generate data continuously, including files, images, backups, logs, databases, and application content.
Storage services ensure that data remains available even after compute resources stop running.
Most cloud platforms provide three primary storage types:
- Object Storage
- Block Storage
- File Storage
The figure below illustrates the major storage categories commonly used in cloud environments.
Engineer Perspective
Engineers use storage services for:
- Application files
- Backup repositories
- Log archives
- Static website content
- Data lakes
Architect Perspective
Architects evaluate storage solutions based on:
- Performance requirements
- Durability
- Scalability
- Cost
- Data lifecycle requirements
Storage decisions often influence the overall architecture of a system.
Networking
What It Does
Networking connects cloud resources together.
Applications rarely operate in isolation. They communicate with users, databases, APIs, external services, and other workloads.
Networking provides the communication layer that makes these interactions possible.
Common networking components include:
- Virtual networks
- Subnets
- Route tables
- DNS
- Load balancers
- VPNs
- Private connectivity
The figure below illustrates how networking connects users to cloud workloads.
Engineer Perspective
Engineers configure:
- Virtual networks
- Routing
- Connectivity
- DNS
- Load balancing
Architect Perspective
Architects design:
- Network segmentation
- Hybrid connectivity
- Multi-cloud connectivity
- Traffic patterns
- Resilience strategies
Networking is often one of the most critical design decisions in enterprise cloud environments.
Identity
What It Does
Identity determines who can access cloud resources and what actions they can perform.
Every cloud platform must answer two questions:
- Who are you?
- What are you allowed to do?
Identity services provide authentication and authorization for users, applications, services, and automation workflows.
The figure below illustrates the basic flow of cloud identity management.
Engineer Perspective
Engineers work with:
- User accounts
- Groups
- Roles
- Service accounts
- API credentials
Architect Perspective
Architects focus on:
- Least privilege
- Federation
- Zero Trust principles
- Identity governance
- Enterprise access strategies
Identity is often called the new security perimeter because almost every cloud security decision eventually becomes an identity decision.
Architect’s Tip
Many cloud outages, security incidents, and compliance failures originate from identity misconfigurations rather than infrastructure failures.
Understanding identity early will make networking, security, governance, automation, and multi-cloud architecture significantly easier to understand later in the learning series.
Security
What It Does
Security protects cloud resources, applications, identities, and data from unauthorized access and threats.
While identity determines who can access resources, security provides the controls that protect those resources once they exist.
Security is not a separate service. It spans every cloud building block.
Common cloud security capabilities include:
- Identity and Access Management (IAM)
- Encryption
- Firewalls
- Security Groups
- Key Management
- Threat Detection
- Compliance Monitoring
- Security Logging
Modern cloud security follows a Zero Trust approach:
Never trust. Always verify.
The figure below illustrates how security surrounds and protects cloud workloads.
Engineer Perspective
Engineers configure:
- IAM permissions
- Encryption settings
- Security groups
- Firewall rules
- Security monitoring
Architect Perspective
Architects design:
- Zero Trust architectures
- Security boundaries
- Compliance controls
- Governance frameworks
- Defense-in-depth strategies
Databases
What It Does
Databases store structured application data.
Almost every business application relies on databases to store:
- Customer information
- Orders
- Transactions
- Inventory
- User profiles
- Application state
Cloud providers offer both managed and self-managed database services.
Common database categories include:
- Relational Databases
- NoSQL Databases
- Distributed Databases
- Data Warehouses
The figure below illustrates how databases fit into a typical application architecture.
Engineer Perspective
Engineers manage:
- Database instances
- Backups
- Replication
- Performance tuning
- Data migrations
Architect Perspective
Architects evaluate:
- Scalability
- Availability
- Data consistency
- Disaster recovery
- Cost optimization
Observability
What It Does
Observability provides visibility into cloud environments.
Without observability, teams cannot understand how applications are performing or why failures occur.
Observability helps answer questions such as:
- Is the application healthy?
- Why is performance degrading?
- What caused the outage?
- Which component is failing?
Modern observability platforms combine:
- Metrics
- Logs
- Traces
- Alerts
The figure below shows the four pillars of modern observability.
Engineer Perspective
Engineers use observability tools for:
- Troubleshooting
- Monitoring
- Alerting
- Performance analysis
Architect Perspective
Architects define:
- Monitoring standards
- Operational SLAs
- Reliability strategies
- Telemetry architecture
Automation
What It Does
Automation creates and manages cloud resources without manual intervention.
As cloud environments grow, manual processes become difficult to maintain.
Automation improves:
- Consistency
- Speed
- Reliability
- Scalability
- Governance
Modern cloud automation commonly uses:
- Infrastructure as Code (IaC)
- CI/CD Pipelines
- Configuration Management
- Policy as Code
- Platform Engineering Workflows
The figure below illustrates how automation creates cloud resources.
Cloud Building Blocks Across the Five Major Providers
The names of cloud services differ across providers, but the underlying building blocks remain remarkably similar.
One of the most important lessons in multi-cloud architecture is understanding that service names are temporary, but architectural concepts are permanent.
Engineers who learn EC2, Azure VMs, Compute Engine, OCI Compute, and IBM Virtual Servers separately often struggle to transfer knowledge across providers.
Engineers who understand the concept of compute can quickly adapt to any cloud platform.
The table below highlights representative services that implement each building block across AWS, Azure, Google Cloud, OCI, and IBM Cloud.
How Cloud Building Blocks Work Together
Cloud applications rarely use a single building block.
Instead, multiple building blocks collaborate to deliver a complete solution.
The figure below illustrates a simplified cloud application architecture.
Key Insight
Individual cloud services are not the goal.
Applications are the goal.
Cloud building blocks simply provide the capabilities required to deliver applications, platforms, data services, AI workloads, and business outcomes.
Building Blocks of Multi-Cloud Architecture
One of the biggest misconceptions about multi-cloud is that it requires completely different architectural thinking.
In reality, multi-cloud environments are built using the same building blocks discussed throughout this lesson.
The difference is that those building blocks may be distributed across multiple cloud providers.
The figure below illustrates a simplified multi-cloud architecture.
The diagram below shows how organizations can combine services from multiple providers to create a unified architecture.
Key Insight
Multi-cloud architecture is not about using multiple providers.
It is about selecting the best building blocks from multiple providers to meet business, technical, operational, and regulatory requirements.
Multi-Cloud Building Block Strategy
Beginners often think about cloud providers first.
Experienced architects think about building blocks first.
Traditional Thinking
❌ AWS Architecture
❌ Azure Architecture
❌ Google Cloud Architecture
Multi-Cloud Thinking
✅ Compute Strategy
✅ Identity Strategy
✅ Networking Strategy
✅ Security Strategy
✅ Data Strategy
This shift in thinking is one of the most important transitions from engineer to architect.
Architect’s Recommendation
When evaluating cloud providers, focus less on service names and more on how each provider delivers:
- Compute
- Storage
- Networking
- Identity
- Security
- Data
- Observability
- Automation
This creates architectures that remain flexible as technology evolves.
Agentic AI Impact on Cloud Building Blocks
Cloud architecture is entering a new phase where AI and autonomous agents are becoming part of everyday operations.
While the fundamental building blocks remain unchanged, AI is influencing how those building blocks are designed, secured, monitored, and managed.
Compute
AI workloads introduce:
- GPUs
- AI accelerators
- High-performance compute clusters
Identity
Organizations are beginning to manage:
- Agent identities
- Service identities
- Machine identities
alongside traditional user accounts.
Security
Security teams must now consider:
- AI access controls
- Agent permissions
- Prompt injection risks
- Model governance
Observability
Modern observability platforms increasingly monitor:
- AI model performance
- Agent behavior
- Inference latency
- AI cost metrics
Automation
AI-assisted automation is becoming common for:
- Infrastructure provisioning
- Troubleshooting
- Incident response
- Cost optimization
Architect’s Note
AI is not replacing cloud building blocks.
AI is becoming another workload that depends on the same foundational building blocks that support every cloud application.
Engineer vs Architect Perspective
The figure below highlights how engineers and architects typically view cloud building blocks differently.
The diagram below compares day-to-day engineering responsibilities with architectural responsibilities.
Common Mistakes and Misconceptions
Learning Service Names Before Concepts
Understanding EC2 is useful.
Understanding compute is more valuable.
Ignoring Identity
Identity is often treated as a security feature instead of a foundational building block.
Treating Security as a Separate Layer
Security should be integrated into every building block.
Designing Without Observability
Systems that cannot be observed cannot be operated effectively.
Relying on Manual Operations
Cloud environments grow rapidly.
Automation becomes essential as scale increases.
Practical Checklist Before Deployment
Before deploying a workload, verify that the core building blocks have been considered.
Infrastructure Checklist
✓ Compute platform selected
✓ Storage requirements identified
✓ Network architecture designed
✓ Identity controls configured
✓ Security requirements defined
✓ Database requirements understood
✓ Monitoring enabled
✓ Automation strategy established
Multi-Cloud Checklist
✓ Workload placement decisions documented
✓ Identity federation requirements reviewed
✓ Security standards applied consistently
✓ Monitoring centralized where possible
✓ Automation standards defined
Key Takeaways
- Every cloud platform is built using common architectural building blocks.
- Compute, Storage, Networking, Identity, Security, Databases, Observability, and Automation form the foundation of cloud computing.
- Cloud providers use different service names, but the underlying concepts remain similar.
- Multi-cloud architectures are created by combining building blocks across providers.
- Understanding architectural concepts is more valuable than memorizing individual services.
- AI and Agentic AI are influencing how cloud building blocks are managed, but the underlying foundations remain the same.
What’s Next
Now that you understand the core building blocks of cloud computing, the next step is learning how those resources are actually created and managed.
In the next lesson:
How Cloud Resources Are Created: Console, CLI, SDK, API and Infrastructure as Code
You will learn:
- How cloud resources are provisioned
- The difference between manual and automated deployment methods
- Infrastructure as Code fundamentals
- Multi-cloud provisioning approaches
- How AI and automation are transforming cloud operations
Understanding how resources are created is the bridge between learning cloud concepts and operating real cloud environments.
