3 ms·
This is really neat, but the high-availability story is concerning--it's the first thing I look at with new services, especially datastores. "Leader-follower" i
by eropple 11y ago
This is really neat, but the high-availability story is concerning--it's the first thing I look at with new services, especially datastores. "Leader-follower" is very easy to implement, but quorum-based election has gotten super easy to deal with over the last couple years and is much better for redundancy, while--being optional--doesn't necessarily have to sacrifice single-node performance for trivial cases.
If it wasn't Go, which I don't enjoy writing, I might consider taking some time this weekend to do it myself, but I don't have a real need for a geolocation store right now and don't have enough interest to overcome having to use Go.
- tidwall 11y agoThanks a ton for the kind words. I have a raft branch that I've been working on for a while, but the performance is not yet there. Currently the replication model is a good place to start with basic redundancy. The scaling features are high on my priority list.
- eropple 11y agoI'm glad to hear that - I can see some really useful applications for this, and I'll be watching it with interest. A transition step that might make the current replication model more generally useful might be to have a quorum tool (internal, delegating to Consul/ZK/whatever, etc.) just for leader election and use the existing leader/follower logic for that.