Hi Brice, I agree with your nit-picky comment, particularly with respect to the OP's emphasis, but there are many cases where read at ONE is sufficient and performance is "better enough" to justify the possibility of a wrong result. As with anything Cassandra, it's highly dependent on the nature of the workload.
Steve On Fri, Oct 9, 2015 at 12:36 PM, Brice Dutheil <brice.duth...@gmail.com> wrote: > On Fri, Oct 9, 2015 at 2:27 AM, Steve Robenalt <sroben...@highwire.org> > wrote: > > In general, if you write at QUORUM and read at ONE (or LOCAL variants >> thereof if you have multiple data centers), your apps will work well >> despite the theoretical consistency issues. > > Nit-picky comment : if consistency is something important then reading at > QUORUM is important. If read is ONE then the read operation *may* not see > important update. The safest option is QUORUM for both write and read. Then > depending on the business or feature the consistency may be tuned. > > — Brice > > -- Steve Robenalt Software Architect sroben...@highwire.org <bza...@highwire.org> (office/cell): 916-505-1785 HighWire Press, Inc. 425 Broadway St, Redwood City, CA 94063 www.highwire.org Technology for Scholarly Communication
