Follow-Up Regarding Large Scale Changes
Yesterday, I mentioned that teams should own and roll out their large-scale changes.
Some people thought it contradicted the Google SRE ideas, so I want to clarify a couple of things:
- This concept only applies to large-scale changes. It doesn’t change which team owns and is responsible for a service. For example, just because I upgraded the version of Java that your service uses doesn’t mean my team suddenly has to maintain the service.
- It helps to have clear contracts for your service teams and the team implementing the large-scale changes. For example, if there are end-to-end tests, then as long as they pass when I upgrade your Java version, I’m not responsible if the service fails in production.
Like what you've read?
If you're an engineering leader or developer, you should subscribe to my 80/20 DevOps Newsletter. Give me 1 minute of your day, and I'll teach you essential DevOps skills. I cover topics like Kubernetes, AWS, Infrastructure as Code, and more.
Not sure yet? Check out the archive.
Unsubscribe at any time.