Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of brettpthomas@gmail.com
 designates 209.85.216.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=f0XhL7Dv9Eka6lE+c/tZV+Wn87KPei5wmI31gBP4ulMBKpgKSal+6yeJM4FfpBgtM0
         ElTtW4JvjZ6TiE+py90MmhHwJohju4REFAImZBDD35fZdKB8ps7PKjiuh5EEdisoJXdm
         zuLIx4m2Yk93+0T0DRkRWUbqYGQ8dnA/B9WAM=
MIME-Version: 1.0
In-Reply-To: <AANLkTilJhIwMp2Pt148sNyo5BKin9K8ONpW4qnElsWHL@mail.gmail.com>
References: <2B4B52565669304C979DC60E52AA3F9B022C8EF34B@spnvm1183.bud.bpa.gov>
	<AANLkTinJEdgWWCm4EZGO69f8kdgRXlnweJsNH6AKDY2-@mail.gmail.com>
	<AANLkTimo_ymWmiiz3Kso56pNz_svKGuP6hXe8dJTDELS@mail.gmail.com>
	<AANLkTiniPgIZEQFE7jEjrBCRt6jjkvkTXW0RBU2aWXPn@mail.gmail.com>
	<4C38C86B.5070004@cloudeventprocessing.com>
	<AANLkTikA0a_EtyXWQuRSMq2ZAkdv8tV0qDt6_SNOHH-J@mail.gmail.com>
	<AANLkTilJhIwMp2Pt148sNyo5BKin9K8ONpW4qnElsWHL@mail.gmail.com>
Date: Sat, 10 Jul 2010 15:50:23 -0400
Message-ID: <AANLkTimrrUSbCjDTKpNMS2xmrIvhCN9OjtnYHpwQhODH@mail.gmail.com>
Subject: Re: TechCrunch article on Twitter and Cassandra
From: Brett Thomas <brettpthomas@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=00163630f3cf8e3130048b0dd49f

--00163630f3cf8e3130048b0dd49f
Content-Type: text/plain; charset=ISO-8859-1

Idunno, I think understanding those companies' decisions is extremely
relevant for anybody working with cassandra. I really like this thread and
hope it keeps going.

On Jul 10, 2010 3:38 PM, "Sumit Datta" <sumitdatta@gmail.com> wrote:

Hello,
I have been a silent spectator in this list for a long while, and
while I like reading much mail traffic, this one I thought I should
reply to.
You know what I see in all this? More "Twitter" and "Facebook" than
"Cassandra". Are we here to discuss them or the software?
What I do not see are details as to why Cassandra is not being used to
store tweets. Or the details of the implementation that does have
Cassandra.
I for one would love to see discussion on code, design, architecture.
Not just thoughts on company's decisions. Why Twitter took those
decisions is something we should not guess and tell.
Thanks
--
Sumit Datta
brainless.in

--00163630f3cf8e3130048b0dd49f
Content-Type: text/html; charset=ISO-8859-1

<p>Idunno, I think understanding those companies&#39; decisions is extremely relevant for anybody working with cassandra. I really like this thread and hope it keeps going. </p>
<p><blockquote type="cite">On Jul 10, 2010 3:38 PM, &quot;Sumit Datta&quot; &lt;<a href="mailto:sumitdatta@gmail.com">sumitdatta@gmail.com</a>&gt; wrote:<br><br>Hello,<br>
I have been a silent spectator in this list for a long while, and<br>
while I like reading much mail traffic, this one I thought I should<br>
reply to.<br>
You know what I see in all this? More &quot;Twitter&quot; and &quot;Facebook&quot; than<br>
&quot;Cassandra&quot;. Are we here to discuss them or the software?<br>
What I do not see are details as to why Cassandra is not being used to<br>
store tweets. Or the details of the implementation that does have<br>
Cassandra.<br>
I for one would love to see discussion on code, design, architecture.<br>
Not just thoughts on company&#39;s decisions. Why Twitter took those<br>
decisions is something we should not guess and tell.<br>
Thanks<br>
<font color="#888888">--<br>
Sumit Datta<br>
<a href="http://brainless.in" target="_blank">brainless.in</a><br>
</font></blockquote></p>

--00163630f3cf8e3130048b0dd49f--