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.
5 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?