Re:Titan: Distributed Graph Database
by pipeep on Friday September 11, 2015 @12:51PM
(#10204735)
I suppose it's a difference in terminology, but it seems strange for them to state:
> Support for ACID and eventual consistency.
As ACID typically implies strong consistency. To quote the wikipedia page on eventual consistency that they link to:
> Eventually consistent services are often classified as providing BASE (Basically Available, Soft state, Eventual consistency) semantics, in contrast to traditional ACID (Atomicity, Consistency, Isolation, Durability) guarantees.
Re:Titan: Distributed Graph Database
by gkop on Friday September 11, 2015 @01:01PM
(#10204799)
"Support for" implies it's capable of these guarantees independently but doesn't necessarily mean it's capable of both of them simultaneously, IE it may be configured for one or the other.
> Support for ACID and eventual consistency.
As ACID typically implies strong consistency. To quote the wikipedia page on eventual consistency that they link to:
> Eventually consistent services are often classified as providing BASE (Basically Available, Soft state, Eventual consistency) semantics, in contrast to traditional ACID (Atomicity, Consistency, Isolation, Durability) guarantees.