[nrmitchi]

Yes, Cloudflare's offering here has promises of adding more functionality in the future, but I don't think that changes my point. At the moment, it is fundamentally the same as existing tools.

"Worker" functionality is already available on both Netlify and Vercel.

Cloudflare's version will obviously have a tighter integration into the rest of Cloudflare.

I've written up a summary of tools/options in this space in the past (but it is a bit out-of-date, but space is moving fast). Including Cloudflare Pages, I now count 6 platform-add-on features that cover all of this functionality.

https://www.nrmitchi.com/2020/10/state-of-continuous-product...

[TimTheTinker]

It is fundamentally different: concerning service offerings, your static site and your edge cache can both be handled by CloudFlare.

Maybe that’s a nitpick, but it probably feels earth-shattering to some, because it recategorizes CloudFlare as a first-class hosting provider (and soon-to-be application and database layer), not just a cache. Sort of like how Redis is now a first-class database, at least according to them.

Personally, I’m excited about this because it finally represents an edge someone has (no pun intended) that could compete with AWS’s services for JAMStack-style sites and apps.

[elithrar]

> "Worker" functionality is already available on both Netlify and Vercel.

Workers at those providers do not run _at the edge_ for each request. They lean on AWS Lambda to pre-generate or render assets, but you can't reliably run a function there on every user-facing request without a noticeable latency penalty.

[edaemon]

Vercel's functions do run at the edge, but Netlify's are just AWS Lambda functions.

[oapsi]

How is this different than Vercel? We already has a big CF account so it would be easy to move there (we have a bunch of Stackbit sites that are currently deployed on Vercel)