Code Everywhere: Why We Built Cloudflare Workers

&gt; the most peered network on the planet<p>That&#x27;s a bold claim. I&#x27;d expect Akamai, Google and Amazon to be peered at more locations, maybe even more. Or have they become that big?

Very similar to lambda@edge<p>Trade offs I see<p>* Cloudflare is probably slightly closer to customers, but cloudfront is still very close<p>* lambda@edge should be cheaper with amazons scale and ecosystem<p>* cloudfront itself is very expensive compared to Cloudflare, almost every project can integrate Cloudflare and use this, where small projects don’t really make sense for cloudfront

It would be amazing if those workers supported WebSockets. Running game servers in them would be tempting, as long as they don&#x27;t charge exorbitant prices for bandwidth.

This is pretty interesting, especially if one get some kind og local storage where one can cache the data from the users and also keep some extra data one need to handle the requests. One can also imagine some kind of MQ solution that distribute to the edges and then updates the clients (for games and such scenarios)

How does this deal with proxy loops?<p>As an example, I would assume worker is making requests with the internal view of the site, but can not have an internal view of other sites or security problems would ensue.. So what happens when two of my sites have service workers fetching something from each other on each request?

Summary: Service Workers on the Edge Server.<p>Very interesting, especially since it allows for a Cloudflare ESI system.<p>Wonder if many will take advantage of it