Code Everywhere: Why We Built Cloudflare Workers
blog.cloudflare.com
Code Everywhere: Why We Built Cloudflare Workers
1–10 of 28 posts
Re: Code Everywhere: Why We Built Cloudflare Workers
#2This 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)
Re: Code Everywhere: Why We Built Cloudflare Workers
#3Summary: Service Workers on the Edge Server.
Very interesting, especially since it allows for a Cloudflare ESI system.
Wonder if many will take advantage of it
Re: Code Everywhere: Why We Built Cloudflare Workers
#4This 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)
Yes. We are exploring adding data storage at the edge. We would love people’s feedback in the product and what features we need to add.
Re: Code Everywhere: Why We Built Cloudflare Workers
#5Summary: Service Workers on the Edge Server. Very interesting, especially since it allows for a Cloudflare ESI system. Wonder if many will take advantage of it
What is ESI in this context? Edge Server Infrastructure?
Re: Code Everywhere: Why We Built Cloudflare Workers
#6> the most peered network on the planet
That's a bold claim. I'd expect Akamai, Google and Amazon to be peered at more locations, maybe even more. Or have they become that big?
Re: Code Everywhere: Why We Built Cloudflare Workers
#7Summary: Service Workers on the Edge Server. Very interesting, especially since it allows for a Cloudflare ESI system. Wonder if many will take advantage of it
What is ESI in this context? Edge Server Infrastructure?
Edge Side Includes. Imagine putting some sort of template syntax in a file, that file is cached, and when it's called from cache it grabs a file from the remote server based on the template syntax.
Re: Code Everywhere: Why We Built Cloudflare Workers
#8[deleted]
Re: Code Everywhere: Why We Built Cloudflare Workers
#9This 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)
Yes. We are exploring adding data storage at the edge. We would love people’s feedback in the product and what features we need to add.
It sounds like you're slowly working towards becoming some sort of insane hosting company
Re: Code Everywhere: Why We Built Cloudflare Workers
#10> the most peered network on the planet That's a bold claim. I'd expect Akamai, Google and Amazon to be peered at more locations, maybe even more. Or have they become that big?
Yes. We are that big.