I recently came across a use case where I think cockroach may be a good fit.
I got a bit lost in the persuit of answers to the following questions, and I hope you guys can help me figure out whether cockroachdb is a good fit for me.
I have a case of N desktops that would like to work on the same db, all in the same LAN
Running a single DB on any of them (like mysql) is not a good fit, as those are eventually laptops all of them belong to employees that goes in and out of the LAN.
They are all working on a desktop app, that, in the best case scenario, is always writing to a local cockroach db, that is part of the cluster of the LAN and the data is always replicated to everyone else to see the data instantly.
Laptops comes and goes, and I would want data to be fully replicated to all nodes always, such that even if a single node remains, he is the leader and is able to operate alone.
If other laptops join the LAN, they join the cluster and get the replicated data from the single previous instance so that he can go offline and the data survives via the other nodes.
Is that conceivable with cockroachdb?
If I follow the docs for simple cluster of 3 nodes, then If I want to increase it to 5 nodes, I need to increase the replication factor to 5 since otherwise two nodes going down will cause an unavailable range.
While I still dont entirely understand what a range is, I do understand that its not a healthy cluster