zlacker

>>tardis+(OP)
How are you using the workers? Is the JSON cached? Where do you get the JSON?

>>ddoria+g6
I'm using Workers as basically API gateway/smart load balancer to backend services that handle actual load (resource intensive data filtering). Most of the responses are not cached on Cloudflare level. Thing is that I was using Workers for about 4 years already with not issue at at all, I'm aware that I use lots of requests and bandwidth but I just wish I was contacted about mandatory upgrade before effectively turning my service down.

>>tardis+v7
How much are you paying for the workers/month?

Why didn't you use the load-balancer service?

>>ddoria+O7
> Why didn't you use the load-balancer service?

Speaking from experience, if you only need rudimentary L7 load balancing, then Cloudflare Workers is as good as it gets.

> How much are you paying for the workers/month?

Per my estimate, probably between $600 to $2000 for Workers: https://news.ycombinator.com/item?id=34639930

>>ignora+Rg
> Speaking from experience, if you only need rudimentary L7 load balancing, then Cloudflare Workers is as good as it gets.

What would you do in Workers that you couldn't do with Load Balancing? LB handles origin health, can do traffic steering, session affinity etc included. With Workers, you'd need to take care of all that.

I see a point if the Workers do some lifting / caching / transforming etc before passing on the requests, but as a simple load balancer, the actual Load Balancing service seems a better fit.