I don't see Lambda functions in this way, but then again I'm not using them as server replacements as in making them the end points of an API call. I use lambd

I don't see Lambda functions in this way, but then again I'm not using them as server replacements as in making them the end points of an API call. I use lambdas exclusively to process other events generated by S3 or DynamoDB that happen because my web service stored something or directly wants something to happen. This way, I didn't have to write a scheduling system or a batch system for my software, I just use AWS's perfectly good implementations. I don't really see the advantage in specifying my API, tying myself to the AWS authentication infrastructure or trying to encapsulate small bits of my API into Lambdas although I can see why you might do that in a bigger system. For me, the scaling occurs in ECS, not in distributing lambda functions. The better part of "serverless" is the containers running the web system, S3 and the managed service running the database. The lambda functions make the job of longer running tasks much easier to manage and they are terrific for that.