This feels like a step backwards to me, nevermind how necessary it may be. The magic was paying only for what you use on super bursty workloads.
Now this is like throwing your hands up and saying the users bursts are too big for AWS.
Now this is like throwing your hands up and saying the users bursts are too big for AWS.
Yes only paying for the compute you actually use is great, but so is having basically limitless compute power (your wallet willing) without the ops overhead and system maintenance.
Cold starts have been a problem fire a while, and while there many be a better way than this long term, ultimately to some degree the solution will always be keeping a function warm. And that’s ultimately compute, and aws is not likely to give that away.
They also support autoscaling the provisioned concurrency. See here:
https://docs.aws.amazon.com/autoscaling/application/userguid...
Answer could help us try something new. We currently use large google app engine 'apps' after failing to get functions to scale quick enough (and hit limits). we have SUPER bursty traffic that needs to scale up to hundreds of instances very fast.