I would agree with OP with "stay away".

The Google paper Towards Modern Development of Cloud Applications[0] does a great job explaining why.

TL;DR the case they make against micro-services architectures (which Lambda encourages):

    1. It hurts performance
    2. It hurts correctness
    3. It is hard to manage
    4. It freezes APIs
    5. It slows down application development

For even a moderately complex system, spreading logic out over multiple discrete runtimes doesn't make sense; instantly run into each of the 5 points. The only times I've found functions useful is truly single-point behavior where we were running some logic connected to CloudFront on each request for some header parsing.

It is certainly possible to write a monolith in Lambda as well, but then that would be bad architecture and a bad fit and I suppose why they are now introducing this new model that is more like GCP Cloud Run or Azure Container Apps.

[0] https://sigops.org/s/conferences/hotos/2023/papers/ghemawat....