News for hackers. Stuff that matters.
Re:Introducing zetcd by tyingq on Friday May 19, 2017 @08:38PM (#14380359)
Yes, you can sort of detune the whole cluster. That's not quite the same as Consul's and CockroachDB's specific WAN awareness. Those two take different approaches, but do specifically understand and compensate.

>What is your use case?

Contract work, so use case varies. I agree that etcd is often the right answer.

Re:Introducing zetcd by philips on Friday May 19, 2017 @08:44PM (#14380375)
Right, etcd's entire focus is on being a consensus database for distributed systems needing coordination, locking, etc. So, eventually consistent WAN replication hasn't really been a focus.

I do think this sort of cross-cluster key replication is useful and we offer it as a userspace external tool called make-mirror[1].

[1] https://github.com/coreos/etcd/blob/master/etcdctl/README.md...

Re:Introducing zetcd by tyingq on Friday May 19, 2017 @09:05PM (#14380457)
Worth noting that CockroachDB isn't using an eventually consistent model. Yes, it's not the same thing as etcd, but I can see some potential use case overlap.
Re:Introducing zetcd by ideal0227 on Friday May 19, 2017 @09:30PM (#14380551)
There is some overlapping. But we should choose solution wisely :P.

Here is a doc [https://github.com/coreos/etcd/blob/master/Documentation/lea...] comparing etcd with other systems, including CockroachDB.

I work on etcd.