Sounds like a trade-off for extreme scalability

Yes, where needed, but I suspect for most people it's just a trade off of getting buzzword compliance in exchange for slow cold start responses

Shouldn't change your ability to scale. AWS is happy to clone your single lambda an arbitrary amount of times.

The tradeoff is the cold start wait time vs. easy scaling.

Have you actually found cold-start delays to be an issue with serverless services, or are you just speculating? To my knowledge, the cloud provider keeps enough instances hot based on a forecasted demand. I have not found cold-start delays to be a real issue.

AWS doesn’t keep instances warm based on forecasted demand. It uses one instance per request and instances stay warm once they are started for a predetermined amount of time based on the size of tyrvlambda environment.

It depends on the stack. You have to be more mindful of cold start when running Java/Clojure apps, less with JS and .net. There are some good benchmarks out there. There are also some easy ways to keep routes warm, although for certain setups I imagine that could be quite expansive, though still probably not expensive.

I don't know if anything has changed since, but we definitely hot cold start perf issues on lesser used routes at a company I was with 18 months ago.

these individual pages get compiled into a single file with zero dependencies leading to super fast cold start times. I'm a bot, beep boop.