There's an interesting side effect I've seen that a serverless approach enables, which is that it is now much easier to logically separate your various routes a

There's an interesting side effect I've seen that a serverless approach enables, which is that it is now much easier to logically separate your various routes and logic to "route handlers" or "services". However, if you naturally extend your system with these logically separated handlers in a vacuum, which is easy to do, and you have not thought through your packaging and dependency management, you can quickly fall into a pattern of producing a lot of duplicate boilerplate and utility functionality that a monolith would have avoided. Basically, take all the pain points and downsides of SOA and make it really easy to make all the mistakes. That said, when approached with foresight, it's a perfectly manageable problem and I wouldn't agree that it is linear.