What's the difference between Cloudflare Pages and Workers Frameworks?
Basically, when making an app, which should I choose and why? The line between them is really blurry.
12 Replies
Hi veeque! Workers Assets is still in beta, but we're hoping to GA soon. The compatibility matrix best describes differenes between Pages and Worker Assets:
https://developers.cloudflare.com/workers/static-assets/compatibility-matrix/
Cloudflare Docs
Workers vs. Pages (compatibility matrix) · Cloudflare Workers docs
Compatibility matrix for asset hosting on Cloudflare Workers and Pages.
Not all frameworks in Pages are supported with Worker Assets. Additionally, things like static config (header and redirects) aren't currently available with Worker Assets.
i still don't really get who the target audience for that would be? i'm guessing not most of those deploying with cf pages currently?
I have a monolithic (Remix framework) app that is in production on Pages. Because Pages lacks certain things like queue consumption I've had to supplement my app with workers to fill in these gaps. This kind of ruins the goal of keeping everything in one deployment. It's now possible to run Remix on workers, most likely due to the addition of static assets support, so I'm looking to switch from pages to workers.
IMO unless there is something you absolutely need that pages provides, use workers.
I’m not on the Pages/Assets team, so take what I say with a grain of salt.
That said, I believe the goal is to eventually get feature-parity with Pages, and then maybe at some point start migrating people over?
Thanks for this! Where can I find information like this given that I do not work for Cloudflare tho? I'd really like to know things like "hey, we're making this and it will be the way forward, so try adopting it"
I'm relatively new to CF, and trying to figure this out as well. I have what I believe is a pages app (I use wrangerl pages... commands) for a NextJS app. I see in the docs (workers/pages?) that the edge runtime has more packages they support than Vercel. When I go to deploy, I get complaints during the pages build that I need to set the runtime to
edge in certain files which prevents me from using the expanded packages, but if I don't set edge, the build fails. I have the nodejs_compat set in my wrangler.json
Should I be using workers instead? (happy to open a new thread with details if this is noise here)Will cname custom domains be supported for cloudflare workers also?
Aren't they already? I'm currently using a CNAME on my domain for both a deployed worker and through a tunnel to wrangler running the dev setup for the same site locally
I have a bit more understanding of how these are different, I've moved from pages to workers for my project
From my understanding I need to setup my domain within cloudflare for that to work.
But with pages I can setup a api.mydomain.com and only point that subdomain via cname to a pages project within cloudflare without moving the whole domain to cloudflare
workers get a domain like
<worker-name>.<project>.workers.dev you can CNAME to from any DNS provider afaikIs there maybe a special email list we can subscribe to? I know you'e not in the team, but it's curse of replying 😄
I can imagine at some point a decision will be made, even if the feature-par is not 100%.
We can even help test, just don't want to be suddenly in for surprises.