3 ms·
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
by candiddevmike 3y ago
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.
- taylodl 3y agoYou're correct, the team is taking on all that responsibility - which is another reason we use serverless architectures. We have no intention of managing servers, provisioning servers, patching servers, etc. The whole idea of compute has been completely abstracted.