3 ms·
Comparing Workers to Lambda proper seems silly. Lambda lets you connect to DBs, use a lot more than 128MB of memory, etc, etc, etc. Comparing them to Lambda@Ed
by mrkurt 8y ago
Comparing Workers to Lambda proper seems silly. Lambda lets you connect to DBs, use a lot more than 128MB of memory, etc, etc, etc.
Comparing them to Lambda@Edge makes sense, but Lambda@Edge is not a very good product.
(Full disclosure: my company competes with Cloud Flare Workers).
- BillinghamJ 8y agoCould you expand on your opinion of Lambda@Edge? For my company's needs, it has worked superbly.
- mrkurt 8y agoSure! I think it's fine infrastructure-wise, but the dev experience is awful. I like tools you can build, test and run locally, for example. The fundamental problem I run into with Lambda@Edge is just that their request stages aren't a great abstraction (OpenResty/nginx has a similar problem). It really limits what kinds of problems you can solve.
- kentonv 8y ago> The fundamental problem I run into with Lambda@Edge is just that their request stages aren't a great abstraction (OpenResty/nginx has a similar problem). It really limits what kinds of problems you can solve. Yes! I completely agree. Interesting that we both ended up with the Service Workers API instead. I'm really hoping that Service Workers becomes the standard for JavaScript HTTP handling in the future.
- zackbloom 8y agoIf you happen to give Workers a try we would love to hear what you think -> zack [at] cloudflare.com