Ok, it makes scaling technically easy with horizontal scaling for the web tier, ignoring the DB. In practice it makes scaling hard for financial reasons if you

Ok, it makes scaling technically easy with horizontal scaling for the web tier, ignoring the DB. In practice it makes scaling hard for financial reasons if you require 128MB+ per request. A 32GB server will struggle with more than 256 concurrent requests at 128MB+ per request. A 32GB server is an extremely large server for such low request numbers. If you can bring the memory usage down stateless works well. I use a bit of rust on aws lambda with the lowest memory settings so pay fractions of a cent and can handle more traffic than I ever need. I do set up persistent connection pools for the life of the lambda and only bootstrap once to bring down latency per-request but treat it as an ephemeral horizontal scaled service.