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: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default;
 d=cloudeventprocessing.com;
	h=Received:Message-ID:Disposition-Notification-To:Date:From:Reply-To:Organization:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:X-Source:X-Source-Args:X-Source-Dir;
	b=RHMXG+rlu6JTtIfOMok0WEGgfMteLDHxEmOiqHfMiYTCUasIeZERdXggLUctFy/g/yYzDtYB+mz27lvC7BHD01wPdYD/P4pg5KsJ+HszujG90chmuS+Obz4noTsOtL92;
Message-ID: <4C330CAF.6090202@cloudeventprocessing.com>
Date: Tue, 06 Jul 2010 05:59:59 -0500
From: Colin Clark <colin@cloudeventprocessing.com>
Reply-To: colin@cloudeventprocessing.com
Organization: Cloud Event Processing, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
 rv:1.9.1.10) Gecko/20100512 Lightning/1.0b1 Thunderbird/3.0.5
MIME-Version: 1.0
To: user@cassandra.apache.org
Subject: Re: Digg 4 Preview on TWiT
References: <2B4B52565669304C979DC60E52AA3F9B022CC04DC8@spnvm1183.bud.bpa.gov>
	 <1277743872.11218.25.camel@erebus.lan>
	 <1278245675.3878.4.camel@dehora-laptop>
 <1278344422.3283.18.camel@erebus.lan> <4C3306A3.70804@fourkitchens.com>
In-Reply-To: <4C3306A3.70804@fourkitchens.com>
Content-Type: multipart/alternative;
 boundary="------------070905020001060306020403"

This is a multi-part message in MIME format.
--------------070905020001060306020403
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

What were the right questions?  I view Facebook's move away from 
Cassandra as somewhat significant.

And are they indeed using HBase then, and if so, what were the right 
answers?

On 7/6/2010 5:34 AM, David Strauss wrote:
> On 2010-07-05 15:40, Eric Evans wrote:
>    
>> On Sun, 2010-07-04 at 13:14 +0100, Bill de hÓra wrote:
>>      
>>> This person's understanding is that Facebook 'no longer contributes to
>>> nor uses Cassandra.':
>>>
>>> http://redmonk.com/sogrady/2010/05/17/beyond-cassandra/
>>>        
>> Last I heard, Facebook was still using Cassandra for what they had
>> always used it for, Inbox Search. Last I heard, there were no plans in
>> place to change that.
>>      
> I had the opportunity to talk with some Facebook infrastructure
> engineers in San Francisco over the past few weeks. They are no longer
> using Cassandra, even for inbox search.
>
> Inbox search was intended to be an initial push for using Cassandra more
> broadly, not the primary target of the Cassandra design. Unfortunately,
> Facebook's engineers later decided that Cassandra wasn't the right
> answer to the right question for Facebook's purposes.
>
> That decision isn't an indictment of Cassandra's capability; it's
> confirmation that Cassandra isn't everything to everyone. But we already
> knew that. :-)
>
>    

--------------070905020001060306020403
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Calibri">What were the right questions?  I view Facebook's
move away from Cassandra as somewhat significant.<br>
<br>
And are they indeed using HBase then, and if so, what were the right
answers?</font><br>
<br>
On 7/6/2010 5:34 AM, David Strauss wrote:
<blockquote cite="mid:4C3306A3.70804@fourkitchens.com" type="cite">
  <pre wrap="">On 2010-07-05 15:40, Eric Evans wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">On Sun, 2010-07-04 at 13:14 +0100, Bill de hÓra wrote:
    </pre>
    <blockquote type="cite">
      <pre wrap="">This person's understanding is that Facebook 'no longer contributes to
nor uses Cassandra.':

<a class="moz-txt-link-freetext" href="http://redmonk.com/sogrady/2010/05/17/beyond-cassandra/">http://redmonk.com/sogrady/2010/05/17/beyond-cassandra/</a>
      </pre>
    </blockquote>
    <pre wrap="">
Last I heard, Facebook was still using Cassandra for what they had
always used it for, Inbox Search. Last I heard, there were no plans in
place to change that.
    </pre>
  </blockquote>
  <pre wrap="">
I had the opportunity to talk with some Facebook infrastructure
engineers in San Francisco over the past few weeks. They are no longer
using Cassandra, even for inbox search.

Inbox search was intended to be an initial push for using Cassandra more
broadly, not the primary target of the Cassandra design. Unfortunately,
Facebook's engineers later decided that Cassandra wasn't the right
answer to the right question for Facebook's purposes.

That decision isn't an indictment of Cassandra's capability; it's
confirmation that Cassandra isn't everything to everyone. But we already
knew that. :-)

  </pre>
</blockquote>
</body>
</html>

--------------070905020001060306020403--