Re: Evaluating Cassandra for our use case

2010-07-29 Thread Aaron Morton
Thanks for this, Aaron. It does actually look like Redis may be better suited to our needs. I had originally discounted Redis because I had the impression that it had volatile storage only, but now I see that not to be the case. Thanks again! Yup, you've got Append Only, foreground  Snap Shot and

Re: Evaluating Cassandra for our use case

2010-07-29 Thread Russ Brown
On Wed, Jul 28, 2010 at 9:13 PM, Aaron Morton wrote: > Have you considered Redis http://code.google.com/p/redis/? > > It may be more suited to the master-slave configuration you are after. > > - You can have a master to write to, then slave to a slave master, then your > web heads run a local redi

Re: Evaluating Cassandra for our use case

2010-07-28 Thread Aaron Morton
Have you considered Redis http://code.google.com/p/redis/? It may be more suited to the master-slave configuration you are after. - You can have a master to write to, then slave to a slave master, then your web heads run a local redis and slave from the slave master. - Backup at the master or the s

RE: Evaluating Cassandra for our use case

2010-07-28 Thread Daniel Kluesing
>Is it possible to configure Cassandra in such a way that a >node only every asks itself for the data, and if so what sort of >effect will that have on read performance? Check out the RingCache class which lets you make your clients smart enough to ask the right server. (Also, if all nodes have a