SRE for Smaller Organisations
summary
Small organisations apply five practical principles: make everything infrastructure as code (Puppet/Ansible/Chef/Terraform in version control + runbooks) so servers and DR are reproducible and occasionally tested; automate common tasks (example: Jenkins pipelines generated on the fly) but avoid automating once‑a‑year jobs; bake security in early with shared input‑filter libraries; prefer explicit names and simple systems; and prioritise aggregated observability over broad SSH access — think cattle not pets and use error budgets/SLOs for decisions.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:17What is DevOps
- 1:32Toil
- 2:26SRE for smaller organisations
- 3:32Five basic principles
- 4:07Everything should be reproducible
- 7:23Automation
- 9:00Security
- 11:55Visibility
- 13:43Summary
related talks
30mWhen Is SRE Right For You?
43mWhere SRE Can Go Wrong
42mDemystifying SRE and DevOps
25mUnleashing the potential of SRE for modern operations
25mSRE Guiding Principles & Transformational Framework
28mHow to Do SRE When You Have No SRE
52mI’m SRE and You Can Too!—A Fine Manual...
47mPersistent SRE Antipatterns: Pitfalls on the Road to Creating a Successful