Serverless is such a trap. The vendor's need to standardize the execution model is poorly aligned with the developer's need for control and stability over time.

Serverless is such a trap. The vendor's need to standardize the execution model is poorly aligned with the developer's need for control and stability over time. I gave Azure Functions a genuine try and was treated with piles of deprecation notices regarding in proc execution model after just a few months into it. Perhaps AWS is better (I suspect they are), but the concern remains. I don't know how anyone is driving meaningful business value with the amount of distraction these ecosystems bring. I also don't see the scalability argument. Being able to own a whole CPU indefinitely means I can take better advantage of its memory architecture over time. Caches actually have meaning. Latency becomes something you can control. A t2.large running proper software and handling full load for 60 seconds could cost $10-20 if the same were handled in AWS lambda. The difference is truly absurd. TCO-wise, serverless is probably the biggest liability in any cloud portfolio, just short of the alternative database engines and "lakes".