3 ms·
Because ops is overhead in terms of dollars, time, and mental capacity. It’s a pain the get good people, especially after the hype cycle of “devops” this decade
by dpeck 8y ago
Because ops is overhead in terms of dollars, time, and mental capacity. It’s a pain the get good people, especially after the hype cycle of “devops” this decade making every junior IT admin aspiring to it in terms of labels but not skillset due to comp differentials.
To do it right you need people on call, round the clock team, etc. in the end serverless is one of those things that if you can get away with it and chase product market fit while spending a little more on opex while keeping headcount costs down its a no brainer.
It’s not without risk because of course not every problem lends itself to the architecture, it’s very hyped at the moment, many engineers hate it because it’s inelegant/leads to lock in/is different/etc so culturally that’s going to be a minefield if you’re not starting from nothing.