Has anyone here used Cloudflare workers yet? I know they just launched recently.
- Where you using new or existing code (coming from Lambda for example)?
- How did the performance compare?
- Did you run into any difficulties?
1) Working on a project right now that provides edge-level analytics for your sites w/ a focus on privacy: more accurate than Google Analytics (JS blockers remove ~1/3 of your traffic stats) and less icky for your users. Funny this comes up, I'm putting together a list for people who are interested in beta testing, if that sounds appealing: https://xyz.us16.list-manage.com/subscribe?u=0b8a0e873d096aa...
2) Extreme caching on a Wordpress site – using Cloudflare's edge cache WP plugin[1] and the worker from the workers-example repo[2] – currently at a 97% cache hit rate across the site.
update: just double-checked the cache hit stat on Cloudflare, after writing this comment - actually have a 99.95% cache rate as of today (!)
[1] https://wordpress.org/plugins/cloudflare-page-cache/
[2] https://github.com/cloudflare/worker-examples/tree/master/ex...
I'd love to hear more about this – could you elaborate? Any resources you can share to back it up? Thx!
In financial services, we see about 15% higher unique users per day when analyzing HTTP logs versus Google Analytics. In fact, I’ve heard but not verified that GA now applies a “correction factor” to their stats to account for this.
Another approach to this using Workers:
CDNs are designed to forward requests to a origin server and cache the results, but you can serve your site completely from Workers if you embed all the code and data into the deployed script or store content in KV.
Their JavaScript environment/APIs are not standard and there’s no proper spec that I could find.
The debugging environment/IDE is decent for an in-browser one but we had some horrible issues with a stale version being loaded from local storage and accidentally applied to the entire site effectively bringing us down for several minutes.
On every change I also saw several error pages myself during warmup period which made me wonder how many customers were getting them.
This was all ~6 months ago though so things might have improved since then.
Performance wise we’re very happy with it though as it beats the Apache reverse proxy it replaces hands down.
It's not running in a browser so they reimplemented some things but the overall API surface is the same. They also have some extra APIs for CF only features.
Debugging is a problem though, but there's another project called Cloudworker that emulates a local instance: https://blog.cloudflare.com/cloudworker-a-local-cloudflare-w...
You can run CF worker code locally, write tests, etc using our edge app runtime: https://github.com/superfly/fly