Your options are 1. Read & write at quorum 2. Recognize that, in general, if you've got a real need for Cassandra, your data is out of date almost immediately after you've read it no matter what guarantee your DB gives you, so you might as well just forget about ever getting the "right" answer because you probably can't even define what that is.
On Thu, Oct 8, 2015 at 4:17 PM Renato Perini <renato.per...@gmail.com> wrote: > How the two things can fit together? > Cassandra endorses the AP side of the CAP theorem. So how Cassandra can > deliver realtime consistent data? > AFAIK, choosing a consistency level equals to ALL can be a huge > performance hit for C*, so, please, explain me why I should choose C* > for realtime data > that should be consistent across reads after the data has been written. > > Thank you. > >
