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 51A9E7D2D for ; Tue, 4 Oct 2011 20:38:38 +0000 (UTC) Received: (qmail 11209 invoked by uid 500); 4 Oct 2011 20:38:36 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 11184 invoked by uid 500); 4 Oct 2011 20:38:36 -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 11174 invoked by uid 99); 4 Oct 2011 20:38:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Oct 2011 20:38:36 +0000 X-ASF-Spam-Status: No, hits=2.9 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [66.33.216.122] (HELO hapkido.dreamhost.com) (66.33.216.122) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Oct 2011 20:38:29 +0000 Received: from homiemail-a45.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by hapkido.dreamhost.com (Postfix) with ESMTP id 059DA17F68C for ; Tue, 4 Oct 2011 13:38:07 -0700 (PDT) Received: from homiemail-a45.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a45.g.dreamhost.com (Postfix) with ESMTP id 0378B4806C for ; Tue, 4 Oct 2011 13:37:58 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; c=nofws; d=thelastpickle.com; h=from :mime-version:content-type:subject:date:in-reply-to:to :references:message-id; q=dns; s=thelastpickle.com; b=dFLsXTY4Me LzcOeg+bG2IUOPZtYZryzDaPb9sM/6RL/xjB3f5CPGBDLvbzwIKoOmouavSnpfk2 ixylxOOSDiR8StQy3s/9JcjoGgz82sSx6AlycYK5bAHtm7Iyn6XgBNDlSmMenEya waMeCHwPaapq1H+5R+UZnGNo0Houq9mDE= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thelastpickle.com; h=from :mime-version:content-type:subject:date:in-reply-to:to :references:message-id; s=thelastpickle.com; bh=lylEIDazWU2k1Ujc eGz+GIyFHbQ=; b=AxbxvwVOzSdiAOhtuvjZizqVTQgejyb+dq8T8J4XvIFsfnE2 ntkou4UB97bZl4yhpWJiVAPmVwORkIdXVUTeI01YZ0jeoETagsliwQZWCaPlkIe/ aqoHbJ3sho/1SfGRSFXXGUIhjnJMsj2KYBBgQki8kMa0DMXOXHNCvwreHgY= Received: from [172.16.1.4] (222-152-101-125.jetstream.xtra.co.nz [222.152.101.125]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aaron@thelastpickle.com) by homiemail-a45.g.dreamhost.com (Postfix) with ESMTPSA id 22A5448058 for ; Tue, 4 Oct 2011 13:37:41 -0700 (PDT) From: aaron morton Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: multipart/alternative; boundary="Apple-Mail=_30C64F26-865D-4000-9E9F-8D26A4DA5920" Subject: Re: Does anybody know why Twitter stop integrate Cassandra as Twitter store? Date: Wed, 5 Oct 2011 09:37:38 +1300 In-Reply-To: To: user@cassandra.apache.org References: Message-Id: <3284ECB2-8A2F-4A26-86EF-6E54B8F780A5@thelastpickle.com> X-Mailer: Apple Mail (2.1244.3) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_30C64F26-865D-4000-9E9F-8D26A4DA5920 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 If you want to see just how much Twitter uses Cassandra watch Chris = Goffinet's awesome presentation at this years Cassandra SF meeting = http://www.datastax.com/events/cassandrasf2011/presentations Cheers =20 ----------------- Aaron Morton Freelance Cassandra Developer @aaronmorton http://www.thelastpickle.com On 5/10/2011, at 8:16 AM, Paul Loy wrote: > yup, and again it gives a perfectly adequate reason: "Twitter is busy = fighting other fires and they don't have the time to retrofit something = that is (more or less) working, namely their MySQL based tweet storage, = with a completely new technology based on Cassandra." >=20 > If I was in charge of platform at twitter I'd have probably made the = same call. If it aint broke, don't spend $100ks fixing it. Push out new = features that help keep you ahead of the competition. >=20 > I really don't see anything in the closet here. It's just a simple = resource management issue. >=20 > On Tue, Oct 4, 2011 at 11:43 AM, ruslan usifov = wrote: > Hello >=20 > 2011/10/4 Paul Loy > Did you read the article you posted? > Yes > =20 > "We believe that this isn't the time to make large scale migration to = a new technology. We will focus our Cassandra work on new projects that = we wouldn't be able to ship without a large-scale data store. >=20 >=20 > There was big boom in network about, that Tweeter will migrate they = tweets to cassandra, but than they reject this plans. This explanation = sounds very vague. Why they have changed the mind? I find only one = article about this: >=20 > = http://highscalability.com/blog/2010/7/11/so-why-is-twitter-really-not-usi= ng-cassandra-to-store-tweets.html > =20 >=20 >=20 >=20 >=20 >=20 > --=20 > --------------------------------------------- > Paul Loy > paul@keteracel.com > http://uk.linkedin.com/in/paulloy --Apple-Mail=_30C64F26-865D-4000-9E9F-8D26A4DA5920 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 If = you want to see just how much Twitter uses Cassandra watch Chris = Goffinet's awesome presentation at this years Cassandra SF = meeting http= ://www.datastax.com/events/cassandrasf2011/presentations

Cheers
   
http://www.thelastpickle.com

On 5/10/2011, at 8:16 AM, Paul Loy wrote:

yup, and = again it gives a perfectly adequate reason: "Twitter is busy fighting other fires and they don't have the time to retrofit something that is (more or less)=20= working, namely their MySQL based tweet storage, with a completely new=20= technology based on Cassandra."

If I was in charge of = platform at twitter I'd have probably made the same call. If it aint = broke, don't spend $100ks fixing it. Push out new features that help = keep you ahead of the competition.

I really don't see anything in the closet here. It's just a simple = resource management issue.

On Tue, Oct = 4, 2011 at 11:43 AM, ruslan usifov <ruslan.usifov@gmail.com> wrote:
Hello

2011/10/4 Paul Loy <keteracel@gmail.com>
Did you read the article you = posted?
Yes
 
"We believe that this isn't the time to make = large scale migration to a new technology. We will focus our Cassandra work on new projects = that=20 we wouldn't be able to ship without a large-scale data = store.


There was big boom in network = about, that Tweeter will migrate they tweets to cassandra, but than they = reject this plans. This explanation sounds very vague. Why they have = changed the mind? I find only one article about this:

http://highscalability.com/blog/2010/7/11/so-why-is-twit= ter-really-not-using-cassandra-to-store-tweets.html
 





-- =
---------------------------------------------
Paul Loy
paul@keteracel.com
http://uk.linkedin.com/in/paulloy

= --Apple-Mail=_30C64F26-865D-4000-9E9F-8D26A4DA5920--