4 ms·

Concerning the use of this for regular DB connections.. isn't there a bit of a conflict between edge computing, which runs close to the user, and using a regula

Concerning the use of this for regular DB connections.. isn't there a bit of a conflict between edge computing, which runs close to the user, and using a regular centralized DB, which resides in a fixed region?

dknecht 3y ago
With a recent announcement we are addressing this by dynamically moving the code to be close to the data when appropriate - https://blog.cloudflare.com/announcing-workers-smart-placement/ https://blog.cloudflare.com/announcing-workers-smart-placeme...
- slashdev 3y ago
  That's really interesting. Between this and TCP sockets you could now design really interesting distributed, stateful services on Cloudflare Workers. I'd love to design a database for this environment (if you're reading this at Cloudflare, you can hire me to work on this.) I think something that distinguishes between write and read requests, moves writes close to the leader server hosting the data being written, handles reads at the edge, and replicates the deterministic request itself would perform the best and give sequential consistency. This is the approach taken by fauna.com, and it's competitive with Spanner but without the need for GPS and atomic clocks to provide an accurate time source.
  - galactus 3y ago
    I.m guessing they must be doing something like that with their D1 offer
  - ac2u 3y ago
    I wish I could put a bet on cloudflare probably already thinking about acquiring fly.io as they've been working on stuff like this and bumping against all the challenging edges.