3 ms·
The fault tolerance is pretty much flawless. You won't be able to get the database "stuck" or see anomalies. But performance is going to suck if you run serve
by voidmain 8y ago
The fault tolerance is pretty much flawless. You won't be able to get the database "stuck" or see anomalies.
But performance is going to suck if you run server nodes over unreliable connections. I have trouble seeing a FoundationDB cluster running on mobile robots as more than a trade show gimmick. Albeit an awesome gimmick. So in summary you should totally do that.
- dbcurtis 8y agoI can see that. There are various vectors to performance. I hear you saying transactions per second would be unimpressive. A couple of less time sensitive applications are: 1. distrubuting information the entire fleet should eventually know, 2. event log aggregation with fine-grained time alignment among nodes. Both are probably silly problems to solve with a database, killing houseflys with sledghammers and all that, but it never hurts to explore creative tool misuse :)
- alexis_read 8y agoI think Scuttlebutt might be more suitable for you? Extract the text from a conversation on each robot. The offline story is easy here. The other option would be some sort or CRDT-based system - Antidote perhaps?