Nice post! Just a note on the differences between Lambda and Cloudflare workers. Yes, they are different than your traditional Lambda functions sitting behind API Gateway, so your first comparison figure is correct. But they are not drastically different than Lambda@Edge which removes the API Gateway and runs at the CloudFront edge.
Of course, there are very large differences between the two that you hit on, runtime, and the obvious network difference (Cloudflare edge vs Cloudfront edge).
Awesome summary and introduction to Cloudflare workers. I think in general they can be easier to get going with than Lambda@Edge. It might be cool to create a post launching each side by side to compare the challenges.
Nice post! Just a note on the differences between Lambda and Cloudflare workers. Yes, they are different than your traditional Lambda functions sitting behind API Gateway, so your first comparison figure is correct. But they are not drastically different than Lambda@Edge which removes the API Gateway and runs at the CloudFront edge.
Of course, there are very large differences between the two that you hit on, runtime, and the obvious network difference (Cloudflare edge vs Cloudfront edge).
Awesome summary and introduction to Cloudflare workers. I think in general they can be easier to get going with than Lambda@Edge. It might be cool to create a post launching each side by side to compare the challenges.
Yes, sounds like a good idea.