I've seen this notion play out at my own company: use AWS Lambda for everything and don't put too much of anything in one place. This is to avoid creating a mon

I've seen this notion play out at my own company: use AWS Lambda for everything and don't put too much of anything in one place. This is to avoid creating a monolith. Cross-cutting concerns should be put into a lambda layer or (more rarely) a shared library. The issue I see is that most of the problems they're trying to solve this way could be solved with good application architecture.