I’m not sure if Lambda@Edge supports reserved concurrency like standard Lambdas? For standard Lambdas I always set a low reserved concurrency to prevent these s

I’m not sure if Lambda@Edge supports reserved concurrency like standard Lambdas? For standard Lambdas I always set a low reserved concurrency to prevent these situations, deliberately throttling my max executions. Start with the lowest number and if you frequently see throttling you can then increase it. For a three person startup… I find Lambdas/Serverless/Cloudflare workers fantastic if you are clever with how you architect things, they can really bring the costs down to trivial amounts. However you need to be defensive I.e. reserved concurrency etc and clever normally means lots of extra steps/hoops to work around restrictions or use things ingeniously. It’s fun if you like that, if we are honest with ourselves it’s hard to beat the simplicity of a VPS and a full stack framework like Rails or whatever alternative in your language of preference when just starting out, then break specific functionality out in to other architectures as required.