Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 65776 invoked from network); 24 Feb 2010 08:54:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Feb 2010 08:54:44 -0000 Received: (qmail 66555 invoked by uid 500); 24 Feb 2010 08:54:44 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 66509 invoked by uid 500); 24 Feb 2010 08:54:43 -0000 Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-user@incubator.apache.org Delivered-To: mailing list cassandra-user@incubator.apache.org Received: (qmail 66500 invoked by uid 99); 24 Feb 2010 08:54:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Feb 2010 08:54:43 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of cemalettin.koc@gmail.com designates 209.85.218.227 as permitted sender) Received: from [209.85.218.227] (HELO mail-bw0-f227.google.com) (209.85.218.227) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Feb 2010 08:54:35 +0000 Received: by bwz27 with SMTP id 27so85044bwz.20 for ; Wed, 24 Feb 2010 00:54:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=/vPrQZJSOkmdMOjtij8XJ3jBbCcdgdIhV3a9SagjqH0=; b=Tv1aqom6/XeOzYndAtuNQq6Oc5XSUjIYK6YvN5zL9eUkw16t2pb/3Enb10fMnJ2Gie 9BX82WfMoTxH+QgakJrfV6+KOIEWBhqjEAXI3JF35Qcxf4VJjs1wFX1R/di69s4dYZnq lSEIonnQqjw5X4UgA5xG6iGpEKDUD0W5oXOk4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=J9k78wpx9DxwUkK/HgF1mpuHRAZVaFdlOU8VioKrCYYsoC6cc/RToR6nh1l7fzxgNw Ffu2fc3stNcts1a5iDORHgwrtKt7r0MrWUh+Q/D6bWeTDpb3S+VR/v2LEVyt6iAD/8kt SIDdylamTGsVEz3VPbc5NTRNdWkIyx5mH+Qd4= MIME-Version: 1.0 Received: by 10.204.128.82 with SMTP id j18mr2052499bks.133.1267001652128; Wed, 24 Feb 2010 00:54:12 -0800 (PST) In-Reply-To: References: <4e0b5fd61002231534y5ffc7454t81be52ff005efe7@mail.gmail.com> <5f7770581002231651y7f96bb10pc8e159ceb81ac9cc@mail.gmail.com> <4e0b5fd61002232327r6888a5cr85a433dc165be586@mail.gmail.com> From: Cemal Date: Wed, 24 Feb 2010 10:53:52 +0200 Message-ID: <4e0b5fd61002240053h27e335dbof602badf4c20b093@mail.gmail.com> Subject: Re: Help for choice To: cassandra-user@incubator.apache.org Content-Type: multipart/alternative; boundary=0015174a0ef267ad8f048054cf35 X-Virus-Checked: Checked by ClamAV on apache.org --0015174a0ef267ad8f048054cf35 Content-Type: text/plain; charset=UTF-8 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 > > --0015174a0ef267ad8f048054cf35 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi,

Maybe I have to tell that we are very eager to evalu= ate NoSQL approaches and for a simple case we want evaluate and compare eac= h approaches.

In our case actually our data has no= t=C2=A0been 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 p= roblems in some situations. Another difficulty we are dealing with is scali= ng problem. By now we have been using master slaves model but in near futur= e 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 explan= ation about them.=C2=A0

Thanks



On Wed, Feb 24, 2010 at = 10:15 AM, Nathan McCall <nate@vervewireless.com> 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

--0015174a0ef267ad8f048054cf35--