SRE · latency · teaching notes
Cold start SLO budgets for serverless adjacent teams
Cold paths hide inside vendor graphs. We ask cohorts to rebuild a week of production traffic inside a sandbox account, then annotate every step that touches a cold dependency.
Students export percentile tables into a shared spreadsheet template so finance partners can see how latency shifts when concurrency doubles. The exercise is intentionally manual—muscle memory beats dashboards alone.
We close with a short writing sprint: each squad drafts an SLO paragraph that names the user journey, the measurement window, and the rollback owner. No superlatives, just commitments the team can defend in review.