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
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
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
:pickscr...@gmail.com]
Sent: Wednesday, July 28, 2010 4:11 PM
To: user@cassandra.apache.org
Subject: Evaluating Cassandra for our use case
Hi,
I'm currently looking at NoSQL solutions to replace a bespoke system
that we currently have in place. Currently I think the best fit is
Cassandra, but
Hi,
I'm currently looking at NoSQL solutions to replace a bespoke system
that we currently have in place. Currently I think the best fit is
Cassandra, but I would like to get some feedback from those who know
it better before spending more time on it.
Our current system is geared to allowing our
