Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4F38F11504 for ; Fri, 4 Jul 2014 19:45:32 +0000 (UTC) Received: (qmail 52027 invoked by uid 500); 4 Jul 2014 19:45:29 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 51985 invoked by uid 500); 4 Jul 2014 19:45:29 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 51975 invoked by uid 99); 4 Jul 2014 19:45:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jul 2014 19:45:29 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,LOTS_OF_MONEY,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jens.rantil@tink.se designates 209.85.216.173 as permitted sender) Received: from [209.85.216.173] (HELO mail-qc0-f173.google.com) (209.85.216.173) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jul 2014 19:45:25 +0000 Received: by mail-qc0-f173.google.com with SMTP id l6so1791971qcy.18 for ; Fri, 04 Jul 2014 12:45:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tink.se; s=tink; h=date:mime-version:message-id:in-reply-to:references:from:to:cc :subject:content-type; bh=THlzpUa87rKlWCFrQd+yM1ewpLLFYAqDZz0eVhavngI=; b=UGPqo3nVuUK3t9ko8rNQm/Ft6jGpOP/rEW2Jtd0/9fpMDEERCG6tAZVuF5IVTStRZT HDc+XGwf3fiJ7uMWedF5lRKxig9NiLVLzMK0UIyFWaN0Uyuz3qolAZU6iu+pSyMYhjcS GzBnNf9Ic48H3fX0IxVILFRAl7mLPsK4oM/Z4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:mime-version:message-id:in-reply-to :references:from:to:cc:subject:content-type; bh=THlzpUa87rKlWCFrQd+yM1ewpLLFYAqDZz0eVhavngI=; b=OAncIHvtdRXv3js5ZVMnosde3TQHW3P/RXQsNBiXHvZ18DJkubA4ygoAGgvz83KiKh rOheaxMUoAuynhgzRRfzSFbrJC3ZBPEPNWM7wFzq7YdDEI3ripDXugkS6KwnJXST0ZM8 NrCFmJUTDobA9F6dfGDiBLdsE/theOK0vs1o99Sk3TgB4ha497POm3JUDTNqzOMr4pFt Fnpt1IYf4I6WudnQuNnc1W+ZMGPRQnSP+F2cxSq1jGjRQcjzQEcz18CIOGJ4DSiTBIJ6 Nw2IUuDiTqq2wHqW/A4iOclqsbqlEtM/dKnKUzVePLk6vVNhca1+BAjTGyO0exrTw4mf 7vgQ== X-Gm-Message-State: ALoCoQnkgeMQVdjzNjdgH81BepdBBNQiwdHKJmQ7nPuwXZVqWEkaN9yKUO5S7ZY3o1EwJCY6lAR8 X-Received: by 10.229.51.201 with SMTP id e9mr21640926qcg.2.1404503104336; Fri, 04 Jul 2014 12:45:04 -0700 (PDT) Received: from hedwig-22.prd.orcali.com (ec2-54-85-253-234.compute-1.amazonaws.com. [54.85.253.234]) by mx.google.com with ESMTPSA id e8sm57361142qaa.12.2014.07.04.12.45.03 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 04 Jul 2014 12:45:03 -0700 (PDT) Date: Fri, 04 Jul 2014 12:45:03 -0700 (PDT) X-Google-Original-Date: Fri, 04 Jul 2014 19:45:03 GMT MIME-Version: 1.0 X-Mailer: Nodemailer (0.5.0; +http://www.nodemailer.com/) Message-Id: <1404503103311.58a3f3be@Nodemailer> In-Reply-To: References: X-Orchestra-Oid: 45D14D30-B47A-4DB8-941C-19A1D553E004 X-Orchestra-Sig: 8c1c033d645da2d285113f2604b452be46224f6a X-Orchestra-Thrid: T80A81801-1388-4D36-90EB-0696711C54C9_1472708959528660205 X-Orchestra-Thrid-Sig: f0a75cc954c16f503eba4f482218fa2363119dde X-Orchestra-Account: 9db3bb496c9075375a38d31caabbdcb66a3259a3 From: "Jens Rantil" To: user@cassandra.apache.org Cc: user@cassandra.apache.org Subject: Re: Cassandra use cases/Strengths/Weakness Content-Type: multipart/alternative; boundary="----Nodemailer-0.5.0-?=_1-1404503103837" X-Virus-Checked: Checked by ClamAV on apache.org ------Nodemailer-0.5.0-?=_1-1404503103837 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, I think you are asking the wrong first question. You should start with = =22What are my requirements=3F=22. If you are only storing two items that = are rarely ever modified, any database is a good approach. We have no idea = what your use case is. We could speculate about it, but really it all boils= down to one or multiple applications. Don't use a hammer if don't know what to use it for. As to your CTO, your answer to use database X should be =22because it fits = our requirements=22. Simple as that. My five cents, Jens =E2=80=94 Sent from Mailbox On Fri, Jul 4, 2014 at 9:31 PM, Prem Yadav wrote: > Thanks Manoj. Great post for those who already have Cassandra in = production. > However it brings me back to my original post. > All the points you have mentioned apply to any big data technology. > Storage- All of them > Query- All of them. In fact lot of them perform better. Agree that CQL > structure is better. But hive,mongo all good > Availability- many of them > So my question is basically to Cassandra support people e.g.- Datastax = Or > the developers. > What makes Cassandra special. > If I have to convince my CTO to spend million dollars on a cluster and > support, his first question would be why Cassandra=3F Why not this or = that=3F > So I still am not sure about what special Cassandra brings to the = table=3F > Sorry about the rant. But in the enterprise world, decisions are taken > based on taking into account the stability, convincing managers and what > not. Chosen technology has to be stable for years. People should be > convinced that the engineers are not going to do a lot of firefighting. > Any inputs appreciated. > On Fri, Jul 4, 2014 at 7:07 PM, Manoj Khangaonkar > wrote: >> These are my personal opinions based on few months using Cassandra. = These >> are my views. Others >> may have different opinion >> >> >> >> http://khangaonkar.blogspot.com/2014/06/apache-cassandra-things-to-consi= der.html >> >> regards >> >> >> >> On Fri, Jul 4, 2014 at 7:37 AM, Prem Yadav = wrote: >> >>> Hi, >>> I have seen this in a lot of replies that Cassandra is not designed = for >>> this and that. I don't want to sound rude, i just need some info about = this >>> so that i can compare it to technologies like hbase, mongo, = elasticsearch, solr, >>> etc. >>> >>> 1) what is Cassandra designed for. Heave writes yes. So is Hbase. Or >>> ElasticSearch >>> What is the use case(s) that suit Cassandra. >>> >>> 2) What kind of queries are best suited for Cassandra. >>> I ask this Because I have seen people asking about queries and getting >>> replies that its not suited for Cassandra. For ex: queries where large >>> number of rows are requested and timeout happens. Or range queries or >>> aggregate queries. >>> >>> 3) Where does Cassandra excel compared to other technologies=3F >>> >>> I have been working on Casandra for some time. I know how it works and = I >>> like it very much. >>> We are moving towards building a big cluster. But at this point, I am = not >>> sure if its a right decision. >>> >>> A lot of people including me like Cassandra in my company. But it has >>> more to do with the CQL and not the internals or the use cases. Until = now, >>> there have been small PoCs and people enjoyed it. But a large scale >>> project, we are not so sure. >>> >>> Please guide us. >>> Please note that the drawbacks of other technologies do not interest me= , >>> its the strengths/weaknesses of Cassandra I am interested in. >>> Thanks >>> >>> >>> >>> >>> >>> >>> >> >> >> -- >> http://khangaonkar.blogspot.com/ >> ------Nodemailer-0.5.0-?=_1-1404503103837 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi,

I think you are asking the wrong first question. You should start with= =22What are my requirements=3F=22. If you are only storing two items that = are rarely ever modified, any database is a good approach. We have no idea = what your use case is. We could speculate about it, but really it all boils= down to one or multiple applications.

Don't use a hammer if don't know what to use it for.

As to your CTO, your answer to use database X should be =22because it = fits our requirements=22. Simple as that.

My five cents,
Jens
=E2=80=94
S= ent from Mailbox


On Fri, Jul 4, 2014 at 9:31 PM,= Prem Yadav <ipremyadav@gmail.com> = wrote:

Thanks Manoj. Great post for those who already have = Cassandra in production.
However it brings me back to my original post.=
All the points you have mentioned apply to any big data technology.=
Storage- All of them
Query- All of them. In fact lot of them perform better. Agree that CQL= structure is better. But hive,mongo all good
Availability- many of them

So my question is basically to Cassandra support people e.g.- Datastax= Or the developers.=C2=A0
What makes Cassandra special.=C2=A0
If I have to convince my CTO to spend million dollars on a cluster and= support, his first question would be why Cassandra=3F Why not this or = that=3F

So I still am not sure about what special Cassandra brings to the = table=3F

Sorry about the rant. But in the enterprise world, decisions are taken= based on taking into account the stability, convincing managers and what = not. Chosen technology has to be stable for years. People should be = convinced that the engineers are not going to do a lot of firefighting.=

Any inputs appreciated.



On Fri, Jul 4, 2014 at 7:07 PM, = Manoj Khangaonkar <khangaonkar@gmail.com> wrote:
These are my personal opinions based on few months using Cassandra. = These are my views. Others
may have different opinion
regards



On Fri, Jul 4, 2014 at 7:37 AM, = Prem Yadav <ipremyadav@gmail.com> wrote:
Hi,=
I have seen this = in a lot of replies that Cassandra is not designed for this and that. I = don't want to sound rude, i just need some info about this so that i can = compare it to technologies like hbase, mongo, elasticsearch,= =C2=A0solr, etc.

1) what is = Cassandra designed for. Heave writes yes. So is Hbase. Or = ElasticSearch
What is the= use case(s) that suit Cassandra.

2) What kind of queries are best suited for = Cassandra.
I ask = this Because I have seen people asking about queries and getting replies = that its not suited for Cassandra. For ex: queries where large number of = rows are requested and timeout happens. Or range queries or aggregate = queries.

3) = Where does Cassandra excel compared to other technologies=3F

I have been working on Casandra = for some time. I know how it works and I like it very much.= =C2=A0
We are moving towards building a = big cluster. But at this point, I am not sure if its a right decision.= =C2=A0

A lot of people including me like Cassandra in my company. But it has = more to do with the CQL and not the internals or the use cases. Until now, = there have been small PoCs and people enjoyed it. But a large scale project= , we are not so sure.

Please guide us.
Please note that the drawbacks of other technologies do not interest = me, its the strengths/weaknesses of Cassandra I am interested in.
Thanks

=C2=A0







--
http://khangaonkar.blogspot.= com/


------Nodemailer-0.5.0-?=_1-1404503103837--