infrastructure

DevOps Academy

from first deploy to production discipline

One continuous course — infrastructure, networks, Linux administration, and DevOps. Russian text, English terms. Every chapter answers WHAT / WHY / WHEN: what it is, why it exists, and when to apply it.

the numbers

The course at a glance

29chapters

8stages on the path

the path

How the path is ordered

Linux and networking come first — everything else stands on them
Administration and Docker turn a machine into a deployable unit
Kubernetes, CI/CD, and Terraform industrialize the delivery
Observability, SRE, FinOps, and DevSecOps keep it alive in production

The order is the argument: each stage borrows the vocabulary of the previous one, so nothing is memorized that has not been deployed at least once.

the format

WHAT / WHY / WHEN

Every chapter is built on three questions. WHAT — the mechanism in one page. WHY — the failure it prevents, with a real incident as the witness. WHEN — the operating conditions that justify the tool.

If a chapter cannot answer all three, it does not ship.

progress

Reading progress is local

Progress is stored in the browser (localStorage) — no account, no server state, no tracking. The library serves files; the reader owns the bookmark.