News for hackers. Stuff that matters.
Re:Anna: A Fast, Scalable, Flexibly Consistent Key-Value Store by tracker1 on Friday March 09, 2018 @04:36PM (#16555271)
All the options you mention have varying features that give it advantages and disadvantages in various scenarios. What works well in on, won't in others, etc.

That said, I was mostly interested on how this compares to etcd, since the use case seems pretty similar. How does Anna scale out (differing data centers) compared to it being a bad idea with etcd for example.

Re:Anna: A Fast, Scalable, Flexibly Consistent Key-Value Store by doorbumper on Sunday March 11, 2018 @01:45AM (#16561954)
I've just finished reading the paper. One difference is that Anna offers a weaker form of consistency than etcd. Etcd offers sequential consistency, and Anna offers casual consistency. I believe that this could eliminate many etcd use cases, since ordering for non-casual events many be different depending on the node you access.

I'm not sure I fully understand etcd's durability guarantees. When an operation is completed, does that mean that the data is durable on a single machine, and then becomes durable on other machines at a later point? If so, it seems like Anna could offer the same durability guarantees.

I think Anna's architecture could be more of a competitor to Cassandra, or DynamoDB as long as you only need casual consistency. The performance implications do seem pretty interesting.

Re:Anna: A Fast, Scalable, Flexibly Consistent Key-Value Store by jaricftw on Sunday March 18, 2018 @10:53PM (#16615936)
etcd does not provide key partitioning/sharding, it achieves linearizable consistency using replica state machine via Raft. Anna provides weaker consistency guarantee (causal or read committed), but has partitioning/sharding.