It depends on the scale you're operating at, not to be cliche. A small service with simple scaling constraints and that's designed intentionally to scale horiz

It depends on the scale you're operating at, not to be cliche. A small service with simple scaling constraints and that's designed intentionally to scale horizontally or vertically can make use of a lot of our the box systems that a single developer or even team of software engineers could wrangle. If the service needs better security guarantees, scaling triggered by advanced/atypical metrics, or cutting edge performance and tuning then you still need specialized people to realize those systems and maintain them. That's not to underscore how quickly a distributed system starts to get "chatty" and quickly falls into this space. Really all DevOps fundamentally meant was spreading APIs to all kinds of things in infrastructure that previously did not have APIs. Someone, unfortunately, took the leap that it also meant SWEs could do this now - ignoring huge domains of knowledge about distributed systems scaling, security, and performance that rest within the domain of systems people. In effect, it just meant more systems people need to be coding and doing systems thinking.