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.

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.