Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of grokdata@gmail.com designates
 74.125.82.66 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=hzwXTlJ5+e7aiVkwN80tqchhudcZJ/ogL1eYh6NWtIpNVB5WZMRzIbMHBRYl/JmI8q
         UTQK0MkVh+uqiHUqHOcPiz9jXwjb1KxoEeoezNqXfceZ+3WFqX/oZKTl8ysHRN37wZHB
         5NztJQZHRGR3H0Lx/y9nXNWqAt37oCNGmRyiU=
MIME-Version: 1.0
Date: Wed, 30 Mar 2011 02:11:36 +0200
Message-ID: <AANLkTikiU7fCgTobL=3EDC-rLTu0GN7hgtzdb8sYuj0+@mail.gmail.com>
Subject: Ditching Cassandra
From: Gregori Schmidt <grokdata@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=00261887731624826b049fa805e0

--00261887731624826b049fa805e0
Content-Type: text/plain; charset=ISO-8859-1

hi,

After using Cassandra during development for the past 8 months my team and I
made the decision to switch from Cassandra to MongoDB this morning.  I
thought I'd share some thoughts on why we did this and where Cassandra might
benefit from improvement.

   - The API is horrible and it produces pointlessly verbose code in
   addition to being utterly confusing.  EVERYTHING takes a lot of time to
   implement with Cassandra, and to be frank, it is incredibly tiring.  For
   this reason alone I no longer recommend Cassandra.  If you want an example,
   pick up the O'Reilly book on Cassandra and look through the examples.  Such
   MASSIVE amounts of code for doing nearly NOTHING.  This is ridiculous.
    Didn't this strike anyone else as ridiculous?  It should have!
   - You need to have official client libraries and they need to be
   programmer friendly.  Yes, I know there are nice people maintaining a
   plethora of different libraries, but you need to man up and face reality:
    the chaos that is the Cassandra client space is a horrible mess.
   - It is buggy and the solution seems to be to just go to the next
   release.  And the next.  And the next.  Which would be okay if you could
   upgrade all the time, but what to do once you hit production?

I would recommend that everyone interested in improving Cassandra take the
day off,  download MongoDB and read
https://github.com/karlseguin/the-little-mongodb-book . Then, while you are
downloading, unpacking, looking at what was in the JAR, reading the book and
pawing through the examples: _pay attention_ to the neatness and the
effortlessness the ease with which you can use MongoDB.  Then spend the rest
of the day implementing something on top of it to gain some hacking
experience.

No, really.  Do it.  This is important.  You need to connect with the user
and you need to understand what you ought to be aspiring to.

In any case, thanks for all the effort that went into Cassandra.  I will
check back from time to time and perhaps in a year or so it'll be time to
re-evaluate Cassandra.

PS: one last thing.  It took us less time to rewrite the DB-interface for
our system to MongoDB AND port over our data than it took to write the
Cassandra implementation.

~G

--00261887731624826b049fa805e0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

hi,<div><br></div><div>After using Cassandra during development for the pas=
t 8 months my team and I made the decision=A0to switch from Cassandra to Mo=
ngoDB this morning. =A0I thought I&#39;d share some thoughts on why we=A0di=
d this and where Cassandra might benefit from improvement.</div>
<div><ul><li>The API is horrible and it produces pointlessly verbose code i=
n addition to being utterly confusing. =A0EVERYTHING takes a lot of time to=
 implement with Cassandra, and to be frank, it is incredibly tiring. =A0For=
 this reason alone I no longer recommend Cassandra. =A0If you want an examp=
le, pick up the O&#39;Reilly book on Cassandra and look through the example=
s. =A0Such MASSIVE amounts of code for doing nearly NOTHING. =A0This is rid=
iculous. =A0Didn&#39;t this strike anyone else as ridiculous? =A0It should =
have!</li>
<li>You need to have official client libraries and they need to be programm=
er friendly. =A0Yes, I know there are nice people maintaining a plethora of=
 different libraries, but you need to man up and face reality: =A0the chaos=
 that is the Cassandra client space is a horrible mess.</li>
<li>It is buggy and the solution seems to be to just go to the next release=
. =A0And the next. =A0And the next. =A0Which would be okay if you could upg=
rade all the time, but what to do once you hit production?</li></ul><div>I =
would recommend that everyone interested in improving Cassandra take the da=
y off, =A0download MongoDB and read=A0<a href=3D"https://github.com/karlseg=
uin/the-little-mongodb-book">https://github.com/karlseguin/the-little-mongo=
db-book</a>=A0. Then, while you are downloading, unpacking, looking at what=
 was in the JAR, reading the book and pawing through the examples: _pay att=
ention_ to the neatness and the effortlessness the ease with which you can =
use MongoDB. =A0Then spend the rest of the day implementing something on to=
p of it to gain some hacking experience.</div>
</div><div><br></div><div>No, really. =A0Do it. =A0This is important. =A0Yo=
u need to connect with the user and you need to understand what you ought t=
o be aspiring to.</div><div><br></div><div>In any case, thanks for all the =
effort that went into Cassandra. =A0I will check back from time to time and=
 perhaps in a year or so it&#39;ll be time to re-evaluate Cassandra.</div>
<div><br></div><div>PS: one last thing. =A0It took us less time to rewrite =
the DB-interface for our system to MongoDB AND port over our data than it t=
ook to write the Cassandra implementation.</div><div><br></div><div>~G</div=
>

--00261887731624826b049fa805e0--