It's not even just Lambda, I have mentioned it here before but I've inherited a CRUD application where the read is a separate "application" and because of this

It's not even just Lambda, I have mentioned it here before but I've inherited a CRUD application where the read is a separate "application" and because of this I have two databases with minimal differences with multiple applications that are basically the same. On the other hand, I've decreased costs significantly in previous positions by moving the cart functions to a lambda because it made it highly responsive, scaled up to thousands of transactions a second without concern during initial sales of certain fruit based devices which generate a rush, but basically sit idle 90% of the rest of the time. I am not concerned with "the death of serverless", there is a time for lambda, and a time for long running processes. You can stick multiple rest endpoints in a single lambda, and that's the recommended thing to do. Moving from micro to monolith isn't the death of serverless, people not knowing when the appropriate time to use different techniques will be.