I feel like we're headed in a direction where serverless means "removing things developers have to deal with" when it should be "removing things the business as a whole has to deal with", and we're losing the recognition those are often not well-aligned.
@ben11kehoe could you give an example of where this goes poorly?
@ben11kehoe I think I get it. What we want is the simplest expression of business process, with the least amount of operational overhead.
If you go from managing hosting of a software product to writing a ton of custom FaaS code, that's might not be a win.
Is the right?
@acjay exactly! Sometimes wrestling with an annoying product/interface for a day has lower total cost of ownership (i.e., better for the business) than coding for an hour that you now have ops and maintenance for
@acjay Step Functions is a good example of very low TCO (versus, say, Lambda or container-based orchestration) but used to be super annoying to get working (it's gotten a lot better!)
@acjay Without naming names, there is a lot of effort towards "just write code" as if custom code should remain the central purpose of a developer