cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nathan McCall <>
Subject Re: Help for choice
Date Wed, 24 Feb 2010 09:48:56 GMT
I found the following helpful:

There is enough variation in the designs of NoSQL systems that the
only way to really compare them is to take some realistic sample of
your data and how it is accessed and see how each system performs.

I like Cassandra because of it's focus on partition tolerance and
availability in exchange for "eventual consistency" (see for more on
this concept).


On Wed, Feb 24, 2010 at 12:53 AM, Cemal <> wrote:
> Hi,
> Maybe I have to tell that we are very eager to evaluate NoSQL approaches and
> for a simple case we want evaluate and compare each approaches.
> In our case actually our data has not been denormalized yet and we are
> suffering from a lot of joins. And because of very much updates in joined
> tables we have a great performance problems in some situations. Another
> difficulty we are dealing with is scaling problem. By now we have been using
> master slaves model but in near future it seems that we will come across a
> lot of problems.
> By the way I tried to find an article about use cases, pros and cons of each
> NoSQL solution but I could not find a detailed explanation about them.
> Thanks
> On Wed, Feb 24, 2010 at 10:15 AM, Nathan McCall <>
> wrote:
>> The workload you originally described does not sound like a difficult
>> job for a relational database. Do you have any more information on the
>> specifics of your access patterns and where you feel that an RDBMS
>> might fall short?
>> -Nate

View raw message