3 ms·

Same (blue) boat here. To be honest, how Cloudflare Workers work is a bit of a mystery to me as I've only done some very basic prototyping with the service (an

Same (blue) boat here. To be honest, how Cloudflare Workers work is a bit of a mystery to me as I've only done some very basic prototyping with the service (and not really focusing on the "edge" aspect of them), but it seems like the important "stuff" that makes them what they are is how they are deployed. I am REALLY going to show my ignorance here, but is there some chance that the idea is these "workers" are intended to be deployed in the users browser for example, as actual service workers or something? i.e. is this more of a framework for creating service workers vs running in the "backend"?

emj 5y ago
Cloudflare workers are executed on servers and quickly thrown away, they use APIs that make this clear as well, it has nothing to do with service workers. Could you expand a bit on you question?
ushakov 5y ago
i think cloudflare worker is basically like a browser tab the only difference is that your browser is cloudflare and globally-distributed
beepbooptheory 5y ago
Cloudflare workers != js workers. Kinda seems like that's what you are talking about at the end. In my understanding, Cloudflare workers, and "edge" stuff generally, are more like ephemeral server processes that can happen per request, which are backed by some kind of extensive infrastructure that cloudflare, aws, et al can provide. Its not a server, but the promise a server will be there if someone hits that endpoint. Anything client side is not changed.
- ethbr0 5y ago
  Serverless is compute execution, pure and OS-less. The genius of Cloudflare Workers is that it couples the one place Cloudflare beats Amazon (their global ubiquity and edge deployment) into a product feature that a customer cares about. The real genius of AWS at all wasn't "We can sell a thing people will buy" but rather "We can sell excess capacity on a thing we have to have, in order to offer {other, core product}." And Cloudflare has to have network connectivity and minimal latency.

emj 5y ago

Cloudflare workers are executed on servers and quickly thrown away, they use APIs that make this clear as well, it has nothing to do with service workers. Could you expand a bit on you question?

ushakov 5y ago

i think cloudflare worker is basically like a browser tab the only difference is that your browser is cloudflare and globally-distributed

beepbooptheory 5y ago

Cloudflare workers != js workers. Kinda seems like that's what you are talking about at the end. In my understanding, Cloudflare workers, and "edge" stuff generally, are more like ephemeral server processes that can happen per request, which are backed by some kind of extensive infrastructure that cloudflare, aws, et al can provide. Its not a server, but the promise a server will be there if someone hits that endpoint. Anything client side is not changed.

ethbr0 5y ago
Serverless is compute execution, pure and OS-less. The genius of Cloudflare Workers is that it couples the one place Cloudflare beats Amazon (their global ubiquity and edge deployment) into a product feature that a customer cares about. The real genius of AWS at all wasn't "We can sell a thing people will buy" but rather "We can sell excess capacity on a thing we have to have, in order to offer {other, core product}." And Cloudflare has to have network connectivity and minimal latency.