Fitness functions: Scaling service consistency
summary
Codifies engineering guidelines into automated checks run centrally against 214 services at Jimdo, with weekly infrastructure tests and enforced ownership. Built a feature flag genitor that fails — complex setup, no follow‑up, alert fatigue, eventually shut off — and a deployment Notifier that finds services without recent pipelines. Initial audit shows 15% violating the deployment rule, 3% deletable, 3% ownerless; central checks plus active follow‑up produce clear, actionable results and ensure services have working CI/CD.
AI-written summary · about
chapters (7)
- 0:00Fitness functions intro
- 2:08Engineering guidelines limits
- 3:35Defining fitness functions
- 5:05Jimdo’s fitness functions
- 6:28Failed flag genitor test
- 8:14Notifier deployment success
- 9:59Key takeaways
related talks
38mBuilding Service Ownership Using Documentation, Telemetry, and a Chance to Make
59mChecking as a Service
46mSix small steps towards continuous delivery
43mServing for the win - Deploys and hosting for the rest of us
24mReady to Go - Measuring Release Fitness at Scale
29mAutomating Continuous Compliance for Scalable SaaS Delivery
52mDevops @Scale
59mDevSecOps Productivity Metrics and Tools