[kennethh]

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)

[jgrahamc]

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.

[johansch]

I guess the most valuable while still feasible thing would be a distributed eventually consistent key-value store (ideally with no-nonsense pricing: just per pay read/write/delete, with a single unit cost regardless how small or big you are - but please do provide an efficient way to delete the entire db, unlike GC Datastore).

Maybe different tariffs based on the percentage of reads that you can serve locally, the average latency or something similar, in order to avoid having to replicate every piece of data to every edge?

[Navarr]

It sounds like you're slowly working towards becoming some sort of insane hosting company

[jgrahamc]

I don’t see us going into hosting. I do see us doing everything that makes sense when you are a few ms from everyone on the planet.

[random023987]

> Run JavaScript Service Workers at the Edge

> We are exploring adding data storage at the edge.

> I don’t see us going into hosting.

You must have your eyes closed then, because that's clearly pushing the camel nose into the Amazon lambda tent.