This addresses only 50% of what SREs contribute. The other 50% is designing the production infrastructure, processes, and tools that facilitate efficient response. Depending on the size of your company, you can of course make do with off-the-shelf solutions, but that’s not scalable part a certain point; creating robust production systems (as opposed to good code) is a specialty like any other.
I've seen this service ownership model fail when implemented across a dozen service teams. Each team was a snowflake in that it's production infrastructure was unique, and not necessarily reliable.
It also assumes that designing production infrastructure or even systems level thinking is a skill that most software developers have. Certainly, enough do that it's common, but it's not universal.
In this particular case, the org standardized on terraform. Some developers welcomed the ability to self-service. Others wanted nothing to do with it.
