It's important to not confuse Lambda for Lambda@Edge. Lambda can be executed in a total of 18 AWS regions (if you don't count GovCloud). More importantly, actua

It's important to not confuse Lambda for Lambda@Edge. Lambda can be executed in a total of 18 AWS regions (if you don't count GovCloud). More importantly, actually running your code in every region would be somewhat tricky, their architecture is built around you deploying to each individually. Lambda@Edge does run on their CDN nodes, but it isn't quite for general-purpose compute, there's a long list of restrictions you can find here: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-requirements-limits.html https://docs.aws.amazon.com/AmazonCloudFront/latest/Develope... If you're interested in the performance differences, I ran some comparisons using Catchpoint a while ago: https://blog.cloudflare.com/serverless-performance-comparison-workers-lambda/ https://blog.cloudflare.com/serverless-performance-compariso... Lambda and Lambda@Edge also deal with things like cold-starts which impact performance irrespective of the breadth of the network. You can see some of those numbers here: https://serverless-benchmark.com/ https://serverless-benchmark.com/