Skip to content

Site Roadmap

Purpose

This roadmap shows how to use the site to build cloud engineering skills in a sequence that moves from concepts to implementation to explanation.

Phase 1: Build The Shared Model

Start with the provider-neutral Foundations section. The goal at this stage is to understand the recurring concerns that exist on every cloud platform.

  • Foundations should give you a working model for networking, identity, compute, storage, data, observability, automation, and cost.
  • Do not rush past these pages just to start deploying services. They make later provider-specific choices much easier to explain.
  • If a concept feels abstract, tie it to a small example system before moving on.

Phase 2: Choose A Provider Path

Pick one provider and work through its landing page, getting started guide, and provider roadmap.

The point is not to avoid multi-cloud thinking. The point is to avoid shallow learning. One strong provider path teaches more than three partial ones.

Phase 3: Learn Services In Project Context

Use service pages when a project or pattern calls for them. This keeps your learning tied to architecture and operations instead of turning into a long reading list.

  • Build the provider project sequence in order.
  • Read the service pages that support the project you are building.
  • Return to the pattern pages to understand why the architecture is assembled that way.

By this point, you should be able to describe not only what the system does, but how it is exposed, secured, deployed, and observed.

Phase 4: Turn Projects Into Explanations

Once you can build the systems, use the pattern pages and the Career section to turn implementation into communication.

  • Summarize the architecture clearly.
  • Explain the tradeoffs behind service selection.
  • Describe what you did for identity, observability, deployment, and cost awareness.
  • Capture what you would improve in a second iteration.

This is the stage where project work becomes portfolio-ready instead of staying as private practice.

Phase 5: Add Depth Deliberately

After the core provider path is comfortable, add specialization.

  • Go deeper into data and analytics.
  • Add AI and agentic workload patterns.
  • Rebuild the same ideas on another provider to strengthen transfer learning.
  • Improve project quality with better CI/CD, security, and operations discipline.

What Good Progress Looks Like

Good progress is not measured by how many service pages you read. It is measured by whether you can do the following.

  • Build a small cloud system end to end.
  • Explain the identity, networking, deployment, and observability choices.
  • Recognize the same architecture pattern across providers.
  • Turn the work into a clear project narrative for interviews or portfolio use.

How This Fits Into Cloud Engineering

Cloud engineering is cumulative. The roadmap is designed so each new step adds more context for security, automation, troubleshooting, and architecture tradeoffs instead of leaving those concerns until the end.

Official References