DevOps Foundations: Trace and Explain a Service
Trace a request through Linux, networking and cloud permissions. Build a diagnostic script, size a small service and defend its operating boundaries.
Trace a request through Linux, networking and cloud permissions. Build a diagnostic script, size a small service and defend its operating boundaries.
Work through the modules in order. Each lesson ends with an exercise and a retrieval check; keep your answers before revealing the explanation. The final project brings the earlier decisions together in a design or incident record you can discuss aloud.
One introductory lesson is public, one lesson opens with free sign-in, and ten require Premium. Progress is a personal reading record. Self-checks and project rubrics do not award a professional certification. All numerical scenarios are teaching fixtures, not reported production results. Commands are read-only or run against local fixtures unless a lesson explicitly describes an optional sandbox.
Next course: Safe Delivery: Infrastructure, Pipelines and Kubernetes.
When you finish, you can
- Build a local JSON-lines diagnostic script with explicit invalid-record accounting, deterministic output and a meaningful empty-input case.
- Distinguish byte capacity, inode exhaustion and deleted open files, then choose a recovery action that preserves incident evidence and avoids unrelated paths.
- Read an infrastructure plan as a proposed sequence of state changes, checking stable resource identity, replacement effects and recovery prerequisites.
- Produce a service map, diagnostic ledger, capacity calculation and recovery decision for a booking API using a supplied evidence pack and a self-review rubric.
BEFORE YOU START · Comfort with a terminal and basic programming. No production Kubernetes or cloud account required.
Syllabus
Read the host
Start with a service map and an evidence ledger. Read process pressure before adding CPU. Write a log summary that rejects bad input.
Follow the request
Separate DNS, TLS and application failures. Give each request a deadline and a retry budget. Explain disk exhaustion without deleting evidence.
Design cloud boundaries
Separate cloud reachability from permission. Size replicas for the zone you lose. Review replacements before applying infrastructure.
Prove the operating contract
Make health checks match the traffic contract. Explain an operating decision with evidence and limits. Capstone: defend a service readiness review.