It all comes down to responsibility. In your example, you're responsible for the full stack including infrastructure (I'm assuming, if not, I feel bad for your infrastructure team). This model works for some developer teams and not for others, either due to lack of expertise, free cycles, or organizational pressure to have developers focus on code only.

Define your responsibility model first, then your infrastructure consumption patterns.