Roadmap · 5 stages · 23 topics

DevOps & Platform

The machine, the network and the pipeline: how code gets to production and stays healthy there.

0%complete

0 of 23 topics done

~18 h 10 min of reading left

Start: The Command Line →

Follow it and the end of each topic suggests the next one on this track.

Stage 10/7 done

The machine

The shell and Git are a platform engineer's daily tools. A container is an ordinary Linux process with walls around it. Memory, system calls and open files explain many “it works on my laptop” surprises.

Code here comes in Go and JavaScript. New to Go? Start with the 90-second Go primer.

Optional side reads (not counted):

Stage 20/6 done

The network

Load balancers, DNS and TLS certificates are the parts of an outage you'll be asked to debug at 3 a.m.

Stage 30/4 done

Containers and cloud

Containers package an app with everything it needs. Infrastructure as code describes your servers in files you can review, repeat and roll back.

Stage 40/3 done

Delivery

A good pipeline makes shipping boring: every change is built and tested automatically, the exact build that passed is the one that ships, and a bad release reaches only a few users before you roll it back.

Optional side reads (not counted):

Stage 50/3 done

Running it

You can't fix what you can't see. Logs, metrics and traces show what's happening, reliability targets say how reliable is reliable enough, and keeping passwords and keys out of code limits the damage when something leaks.

Optional side reads (not counted):