> > For Cassandra to work as a DocumentStore for Oak it needs to be configured > with a Quorum high enough to ensure that all writes are sequentially > eventually consistent. That might kill Cassandras write performance.
Do you think that in a first version it would be acceptable to penalize the availability in favor of consistency?. I am not 100% certain what > will happen if the backend isnt sequentially eventually consistent > One way might be to look for a causal consistency rather than a strict or sequential one. I need to study the problem a bit more in order to understand the guarantees required. Thanks!. -- Juan José Vázquez Delgado CTO Tecsisa C/Quintanavides, 19 Parque Vía Norte Edificio 4, Planta 3, Oficina H 28050 Madrid T: +34 91 182 04 70 F: +34 91 447 05 11 E: [email protected] W: www.tecsisa.com
