> Aren't Cloudflare Workers more comparable to AWS Lambda@Edge than regular Lambda?
Yes that's my point. Unlike AWS Lambda, the usefulness of Cloudflare Workers is very specialized and narrow, like adding response headers or update a response document.
AWS Lambdas on the other hand can run freely for over 15min, have virtually no limit in how much RAM they can use, and can be pushed as a Docker image with a max size of 10GB.
If that is not enough, AWS Lambdas can be tied together into workflows with AWS step function.
Therefore, for anyone to claim that Cloudflare Workers win over AWS Lambdas, either they have no idea what AWS Lambdas are or have no idea what Cloudflare Workers are.
Here is my use case: I have a static site to process form and referral. It used to run on AWS Lambda. I migrated them to Cloudflare workers. Deployment, code editing etc is much easier.
And no, it's fully act as a standalone app. I define the route to to route a part of traffic to the worker, other parts to our pages app.
For me, it works great and replace my aws lambda usage.
Yes that's my point. Unlike AWS Lambda, the usefulness of Cloudflare Workers is very specialized and narrow, like adding response headers or update a response document.
AWS Lambdas on the other hand can run freely for over 15min, have virtually no limit in how much RAM they can use, and can be pushed as a Docker image with a max size of 10GB.
If that is not enough, AWS Lambdas can be tied together into workflows with AWS step function.
Therefore, for anyone to claim that Cloudflare Workers win over AWS Lambdas, either they have no idea what AWS Lambdas are or have no idea what Cloudflare Workers are.