About Site Reliability Engineering
Site reliability engineering (SRE) applies software engineering to operations: you
build the automation, monitoring, and processes that keep services fast, available,
and recoverable. This course follows the order most SREs actually learn it. It starts
with Linux & Operating Systems and
Networking & Protocols, the ground every production system runs
on, then moves to Scripting & Automation so you can replace
manual toil with code.
Next comes Infrastructure as Code: version-controlled, repeatable
environments built with Terraform and Ansible. From there,
Containers & Orchestration covers Docker and Kubernetes, while
CI/CD & Release Engineering covers pipelines, safe rollouts,
canaries, and rollbacks.
Monitoring & Observability covers metrics, logs, traces, and
alerting with tools like Prometheus and Grafana, and
SLIs, SLOs & Error Budgets turns that data into the SRE way of
deciding how reliable a service needs to be and when to slow down releases.
Finally, Incident Management & Postmortems covers on-call,
response roles, and blameless reviews, and
Resilience & Capacity Planning covers load balancing, graceful
degradation, chaos engineering, and forecasting demand: the skills that separate a
service that works from one that stays up when things go wrong.
Content
10 modules
01
Linux & Operating Systems
Processes, memory, file systems, permissions, and systemd, plus the command-line tools used to inspect and troubleshoot a live server.
LinuxProcessessystemd
02
Networking & Protocols
TCP/IP, DNS, HTTP and TLS, load balancers, and firewalls, and how to trace where a request slows down or fails.
TCP/IPDNSTLS
03
Scripting & Automation
Writing Bash and Python or Go tools to eliminate toil, and tracking your work with Git and GitHub or GitLab.
BashPythonGit
04
Infrastructure as Code
Defining servers, networks, and cloud resources in code with Terraform, and configuring them reproducibly with Ansible.
TerraformAnsibleAWS
05
Containers & Orchestration
Packaging services with Docker and running them at scale on Kubernetes, including deployments, scaling, and health checks.
DockerKubernetesHelm
06
CI/CD & Release Engineering
Automating builds, tests, and deploys, and shipping safely with canary releases, blue-green deployments, feature flags, and fast rollbacks.
GitHub ActionsCanary ReleasesGitOps
07
Monitoring & Observability
Collecting metrics, logs, and traces, building dashboards, and writing alerts that page people only when it matters.
PrometheusGrafanaOpenTelemetry
08
SLIs, SLOs & Error Budgets
Choosing the right indicators, setting realistic reliability targets, and using error budgets to balance feature velocity against stability.
SLISLOError Budgets
09
Incident Management & Postmortems
Running on-call rotations and incident response, communicating during outages, and writing blameless postmortems that drive real fixes.
On-CallRunbooksBlameless Postmortems
10
Resilience & Capacity Planning
Designing for failure with redundancy, graceful degradation, and chaos experiments, and forecasting load so capacity arrives before demand does.
Chaos EngineeringLoad TestingAutoscaling
What You Can Do After This Course
By the end of the curriculum you'll have worked through 5 hands-on projects and
covered the core of what a junior to mid-level SRE or platform role expects.
Concretely, you'll be able to:
Troubleshoot production systems: inspect processes, resources, and network paths on Linux to find why a service is slow or down.
Automate away toil: write scripts and tools in Bash, Python, or Go, tracked with Git and shared through GitHub or GitLab.
Manage infrastructure as code: provision and configure environments with Terraform and Ansible so they are repeatable and reviewable.
Run containerized workloads: package services with Docker and deploy, scale, and heal them on Kubernetes.
Ship safely: build CI/CD pipelines with canary or blue-green releases and roll back quickly when something breaks.
Measure and set reliability targets: instrument services, define SLIs and SLOs, and use error budgets to guide release decisions.
Respond and improve: lead incident response, write blameless postmortems, and use chaos testing and capacity planning to prevent the next outage.