Hi Ramya, Scalar DB is one of the options. https://github.com/scalar-labs/scalardb
But, first of all, please re-think about your design if you really need it. For example, If eventual consistency between multiple rows are acceptable, and writes are idempotent, then you should go with C* write with retries simply. Using transaction is basically the last option. Thanks, Hiro On Wed, Nov 28, 2018 at 10:27 PM Ramya K <subscribemailing...@gmail.com> wrote: > > Hi All, > > I'm exploring Cassandra for our project and would like to know the best > practices for handling transactions in real time. Also suggest if any drivers > or tools are available for this. > > I've read about Apache Kundera transaction layer over Cassandra, is there > bottlenecks with this. > > Please suggest your views on this. > > Reagrds, > Ramya. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org For additional commands, e-mail: user-h...@cassandra.apache.org
