Re:Etcd v3: increased scale and new APIs
by lobster_johnson on Thursday June 30, 2016 @10:00PM
(#12013386)
As I understand it, both Paxos and Zab will result in similar performance characteristics, since writes need, by design, to be coordinated with peers and serialized in a strict manner. In this sense, Etcd and ZK are very much alike, irrespective of how they are implemented internally. I wouldn't be surprised if Etcd was found to be faster and more scalable than ZK, however.
[ Parent
| on HN ]
Re:Etcd v3: increased scale and new APIs
by ideal0227 on Thursday June 30, 2016 @10:47PM
(#12013586)
It really depends on how you view the problem. Yes, the latency of agreeing a proposal is similar, which is limited by physical (network latency + disk io). However, there are ways to put more stuff into one proposal (batching) and submitting proposals continuously (pipelining). These optimizations highly depend on the implementations.