What you (and many others here) are objecting to is completely orthogonal to serverless as an architecture. There's nothing about serverless that requires sepa

What you (and many others here) are objecting to is completely orthogonal to serverless as an architecture. There's nothing about serverless that requires separate repositories or even microservices. I know because I have built a 50,000 line serverless application that is a single repository and deploys functionally as a monolith. We also don't use step functions heavily, because, like you say, that's basically a cloud-specific DSL that you could write in a real programming language with only slightly worse visibility. Serverless is, plain and simple, about passing immutable "partial computation" state through events and keeping all mutable long term state in a database.