3 ms·
> DriftDB is a real-time data backend that runs on the edge. What does "on the edge" mean in this context? Can I just run the server part on my own infrastruct
by matt-attack 4y ago
> DriftDB is a real-time data backend that runs on the edge.
What does "on the edge" mean in this context? Can I just run the server part on my own infrastructure? What if I have multiple pods for redundancy, and client web connections might get connected randomly to any of those pods? How would the pods all share state between each other?
- paulgb 4y ago> What does "on the edge" mean in this context? DriftDB has a concept of “rooms”, which are essentially broadcast channels. By “on the edge”, what I mean is that the authoritative server for each room can be geographically located near the participants in that room. In practice, today that means that it can be compiled to WebAssembly and run as a Cloudflare Worker. > Can I just run the server part on my own infrastructure? Kinda. It includes a server that runs locally, but it’s only useful as a development server at this point. Your question about multiple pods is exactly the reason -- unless you have a routing layer that is aware of DriftDB’s “rooms”, it won’t work if you scale it up. We also make https://plane.dev https://plane.dev which provides the routing layer, but it might be overkill for a DriftDB use case.