Hacker News new | ask | show | jobs
by ignoramous 2339 days ago
> You can thank them for making free DDoS protection mainstream

AWS does charge for WAF and Shield, I believe.

I also remember comparing AWS Lambda at Edge vs Cloudflare Workers (though Lambda allows for longer execution times and generally provides more flexibility like RAM, CPU, Runtimes since it runs on a Linux VM vs V8 Isolates for Workers), costs were something like 10x apart.

Can't wait for WebSockets support for Workers.
1 comments
lentil 2338 days ago
> I also remember comparing AWS Lambda at Edge vs Cloudflare Workers ... costs were something like 10x apart.

According to the AWS pricing example[1] 10 million requests per month on Lambda@Edge costs $9.13. The same thing on Cloudflare Workers[2] costs $5.00. So I would expect it to be closer to 2x. Although as you say there's a bit more flexibility with Lambda@Edge so it'll depend on your particular case.

I'm curious if your situation was different somehow that made for such a big cost difference between the two?

[1]https://aws.amazon.com/lambda/pricing/#Lambda.40Edge_Pricing [2]https://workers.cloudflare.com/#plans

link
ignoramous 2338 days ago
$5 includes a generous free tier for Workers KV that can hold upto 10MiB of data against a single key. Cloudflare does not charge for bandwidth consumed, I believe. Also, use of Cloudflare's zonal http-cache is free.

I guess, when I compared, I took Lambda@Edge's per second billing into consideration and not per 50ms (which brings down the RAM usage cost from $62.52 to $3.13 and total usage from $68.52 to $9.13).

What really sealed the deal for me was the very low cold-start times with Workers. I'm not aware of recent improvements with Lambda@Edge, but the last time I tried them, it wasn't uncommon to hit 100ms+ start times.

link
lentil 2338 days ago
That's interesting, thanks. I haven't really used Cloudflare Workers for much myself so it's interesting to hear folks' comparisons.
link
ignoramous 2338 days ago
One more thing, I am not sure if Lambda@Edge charges based on wall-time or cpu-time. Workers' 50ms is cpu-time only and not wall-time. You could, in theory, spend 30s waiting for a fetch to return as awaiting on the network doesn't count against a Workers' 50ms cpu-time limit.

Ref: https://developers.cloudflare.com/workers/about/limits/

link