Build and Operate Reliable Systems
Connect architecture choices to deployment control loops, security boundaries, performance evidence, and safe software delivery.
Curriculum (18 steps)
Use cohesion, coupling, and dependency direction to choose software boundaries that make likely changes easier to contain.
Follow a request from a stable caller through an injected policy interface to one selected implementation.
Refactor a checkout calculation so rate rules can vary without spreading carrier-specific branches through the order workflow.
Turn user requirements into a data flow, capacity model, and failure-aware architecture before drawing infrastructure boxes.
Visualize a client request, routing, cache hit or miss, database access, and the chosen freshness policy.
Follow the cloud control plane that compares declared configuration with live resources and works toward the requested state.
Follow a desired replica count through the API server, controllers, scheduler, node agent, runtime, and readiness checks.
Deploy a small stateless workload, scale it, change its image, and inspect how desired and ready state differ over time.
Threat-model a request by tracing sensitive data, user authority, trust boundaries, and the controls that limit abuse.
Follow a login attempt through rate limits, password-hash verification, authorization context, and a protected session cookie.
Trace untrusted input into a web page, identify the output context, and choose encoding or sanitization at the correct boundary.
Use workload shape, latency distributions, profiling, and controlled experiments to find the cause of slow software.
Follow a request through a saturated connection pool and distinguish queue delay from database execution time.
Measure a Cache-Locality Change
practiceUse a repeatable matrix workload to compare loop order, profile cache behavior, and report what the measurement can support.
Follow a change from Git objects and review through tests, build artifacts, deployment, rollback, and production feedback.
Visualize review, automated checks, immutable artifacts, staged rollout, observability, and rollback decisions.
Follow a reviewed commit through repeatable checks, an immutable artifact, staged deployment, health signals, and promotion.
Use a visual Git sandbox to create branches, merge histories, resolve a conflict, and recover a commit by following references.