Hi XuYi,
I like the idea but I'm unsure if I like the master / slave approach.
We often deal with "Shopfloor" Scenarios where the setup for the Database is
basically "MultiMaster", because we need to sync data one the one hand, but if
a system goes down, everything else should keep working.
Woul
yep, I think the cluster is in P2P mode when they startup. Then a leader
election algorithm will change the cluster into the M/S mode (RAFT
algorithm is qualified). If the master is down, a new master can be elected
and lead the cluster.
By the way, we need to consider the cost of keeping strong c
Hi,
this is a very interesting (and important) question.
I think we should really consider what we can skip (from an application
perspective) and what to keep.
Perhaps a Token Ring architecture like Cassandra uses could also be a good fit,
if we hash on the device id or something.
At least in th
