Cloud Computing Roadmap
Cloud Architect
A cloud architect decides how a system is put together on cloud infrastructure and is accountable for the cost, security and resilience of that decision. It is a senior role: the sequence assumes you can already build and operate something, and adds networking, identity, well-architected trade-offs and the financial literacy the title actually requires.
By the end: Design a cloud system and defend its cost, security and failure behaviour.
The Cloud Architect Roadmap
Systems and Networking~2 months
An architect who cannot explain a packet's journey cannot design for failure.
Linux and systems
Processes, filesystems and resource limits — what your instances are actually running.
Networking fundamentals
IP, routing, NAT, DNS and TCP. More cloud problems are network problems than anything else.
TLS and certificates
Handshake, chains and expiry — the recurring cause of sudden total outages.
HTTP and load balancing
How requests are distributed, and what a health check really proves.
Containers
The deployment unit almost every modern architecture assumes.
Core Cloud Services~2 months
Learn one provider deeply. The second takes weeks.
Compute
Virtual machines, containers and functions — and the cost and cold-start trade-offs between them.
Storage
Object, block and file, plus the storage classes that quietly decide your bill.
Managed databases
When a managed service is worth the premium, and when it constrains you badly.
Serverless
Functions and event-driven services — excellent for spiky work, awkward for long-running.
Messaging and events
Queues, topics and event buses — how services stay decoupled.
CDN and edge
Push content and increasingly compute closer to the user.
Identity, Networking and Security~2 months
The three areas where a design mistake becomes a breach.
Cloud IAM
Roles, policies and least privilege. The most misconfigured surface in every cloud.
VPC design
Subnets, route tables, gateways and peering. Get this wrong and everything above it suffers.
Cloud security posture
Encryption at rest and in transit, key management, and no public buckets.
Zero trust
Stop treating the network perimeter as an authorisation boundary.
Compliance
SOC 2, GDPR and data residency — constraints that shape the architecture, not paperwork afterwards.
Infrastructure as Code~2 months
An architecture that only exists in a console diagram is not reproducible.
Terraform
Providers, modules, state and drift. The lingua franca across clouds.
IaC principles
Immutability, idempotence and review — infrastructure changes go through a pull request.
Native IaC tools
CloudFormation or CDK — you will inherit estates written in them.
Landing zones
Multi-account structure, guardrails and org policy set up before teams arrive.
Kubernetes on cloud
EKS, AKS or GKE when the workload genuinely warrants an orchestrator.
Architecture and Trade-offs~2 months
The judgement the title is actually paying for.
Well-architected thinking
Reliability, security, performance, cost and operations — held in tension, never all maximised.
Resilience and failure design
Availability zones, retries with backoff, and graceful degradation over false promises.
Disaster recovery
RPO and RTO agreed with the business, and a restore you have actually tested.
Cost architecture and FinOps
Egress, reserved capacity and right-sizing. An expensive design gets redesigned.
Migration strategies
Rehost, replatform, refactor — and being honest about which one the budget supports.
Multi-cloud and hybrid, critically
OptionalUsually the wrong answer. Know the few cases where it is not.
Certification and Practice~1 month
Evidence for the people who have not seen your work.
Observability at architecture level
Decide what is measured and alerted on before the system is built, not after the first outage.
Design a system end to end
Diagram it, cost it, then state its failure modes out loud. This is the interview.
Certification
AWS Solutions Architect Associate, then Professional. A screening filter more than an education.
Write it down
Architecture decision records — the habit that separates an architect from a senior engineer.
Interview preparation
Expect trade-off questions with no clean answer. Reasoning is scored, not recall.
Frequently Asked Questions
Do I need certifications to be a cloud architect?
They help more here than in most roles — AWS Solutions Architect and its Azure and GCP equivalents are widely used as screening filters, and partner status pushes consultancies to require them. They are not a substitute for having designed something real, but they get the interview.
Can I become a cloud architect without being a developer?
It is possible from a strong infrastructure or network engineering background, and that path is common. You will still need to read code fluently, because architecture decisions constrain application design and you cannot make them credibly without seeing what they do to the codebase.
How important is cost in cloud architecture?
Central, and it is the part most people underrate. An architecture that works but costs three times what it should will be redesigned, and the architect owns that. Understanding storage classes, egress charges, reserved capacity and the real price of managed services is a core skill, not a finance-team concern.
Multi-cloud — worth it?
Usually not, and architects are often the ones who have to say so. Multi-cloud multiplies the operational surface and forces you down to the lowest common denominator of each provider. The defensible reasons are regulatory or a specific service that exists nowhere else — not vendor lock-in anxiety.