Re:How to Build Software Like an SRE
by dividedbyzero on Monday October 17, 2022 @11:17AM
(#33234680)
But don't you actually want a certain amount of coupling in the operations part? After all you need to ensure they run in a place and in a manner that allows them to find and talk to each other and usually in a combination determined by the goal of a specific deployment, i.e. sometimes you might not need a rail-cargo-service because the customer only ships by truck, etc. Then scaling/autoscaling (if any) needs to be compatible, versions need to be within a certain range, any central data store must be coordinated as well, not to speak of service meshes, chaos experiments and the like. It's a good thing to develop services with minimal coupling, but that stage has different risks and goals from devops/ops, at least in my experience on both sides of the dev/ops transition zone.
[ Parent
| on HN ]
Re:How to Build Software Like an SRE
by mikedelago on Monday October 17, 2022 @11:49AM
(#33235242)
> But don't you actually want a certain amount of coupling in the operations part?
In my opinion, for sure. There's a balance between "too coupled" and "too de-coupled" that should be stricken rather than too far on either side. It's good to say that this is also contextual; some projects may be fine with either more or less coupling than others, and that's OK.
Re:How to Build Software Like an SRE
by thisiswrongggg on Monday October 17, 2022 @02:53PM
(#33237982)
I understand but it is a slippery slope.