Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 95849 invoked from network); 6 Jul 2010 13:22:29 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 6 Jul 2010 13:22:29 -0000 Received: (qmail 57521 invoked by uid 500); 6 Jul 2010 13:22:28 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 57505 invoked by uid 500); 6 Jul 2010 13:22:25 -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 57497 invoked by uid 99); 6 Jul 2010 13:22:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Jul 2010 13:22:24 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of avinash.lakshman@gmail.com designates 209.85.214.172 as permitted sender) Received: from [209.85.214.172] (HELO mail-iw0-f172.google.com) (209.85.214.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Jul 2010 13:22:17 +0000 Received: by iwn38 with SMTP id 38so1002045iwn.31 for ; Tue, 06 Jul 2010 06:21:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=yzITsVPhgijk96Zo0JGDhX0fHWOKvQ92sBcm9p9RkMo=; b=paLw2A28a59muAc/ckvs9UkwngYXNeGEeNUc3B+EVJ269xSZkUkXXyTJtpGdOXlIE1 mJtQJYEDr3GXEFCNXW3v2MDmmqp930+4BtGL/bW2bobwvdtdxXA83Qryy/VoCZxRcB2w JaB4t7eoD21N/PgQJPeN2XjUzKMYaDs5G0GRI= 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=I/2v1xQb0LdEE/+Gs/cnrGgESAzw/4X8HYa+CasFK3m9HjJ3UdBfs9Lo6rcXf0EuaW BTZTgkqK34s6KV/614ZYD3CgFBvd4W9YSwnpzcZfVtlIzi0IJ+95+FrO3wrO/PYmT4Yo M+X4u9tOWXt6A8fkyHtqnWeK54Q8rNCdDWwd0= MIME-Version: 1.0 Received: by 10.231.36.69 with SMTP id s5mr5062124ibd.58.1278422516417; Tue, 06 Jul 2010 06:21:56 -0700 (PDT) Received: by 10.231.85.142 with HTTP; Tue, 6 Jul 2010 06:21:56 -0700 (PDT) In-Reply-To: <4C3306A3.70804@fourkitchens.com> 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> Date: Tue, 6 Jul 2010 06:21:56 -0700 Message-ID: Subject: Re: Digg 4 Preview on TWiT From: Avinash Lakshman To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=000325576002f6c4b4048ab7ef6c X-Virus-Checked: Checked by ClamAV on apache.org --000325576002f6c4b4048ab7ef6c Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable FB Inbox Search still runs on Cassandra and will continue to do so. I shoul= d know since I maintain it :). Cheers Avinash On Tue, Jul 6, 2010 at 3: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=D3ra 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. :-) > > -- > David Strauss > | david@fourkitchens.com > | +1 512 577 5827 [mobile] > Four Kitchens > | http://fourkitchens.com > | +1 512 454 6659 [office] > | +1 512 870 8453 [direct] > > --000325576002f6c4b4048ab7ef6c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
FB Inbox Search still runs on Cassandra and will continue to do so. I = should know since I maintain it :).
=A0
Cheers
Avinash

On Tue, Jul 6, 2010 at 3:34 AM, David Strauss <david@fourkit= chens.com> wrote:
On 2010-07-05 15:40, Eric Evans wrote:
> On Sun, 20= 10-07-04 at 13:14 +0100, Bill de h=D3ra wrote:
>> This person'= s understanding is that Facebook 'no longer contributes to
>> = nor uses Cassandra.':
>>
>> http://redmonk.com/sogrady/2010/05/17/beyon= d-cassandra/
>
> Last I heard, Facebook was still using Cas= sandra 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 w= ith some Facebook infrastructure
engineers in San Francisco over the pas= t 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 ta= rget of the Cassandra design. Unfortunately,
Facebook's engineers la= ter decided that Cassandra wasn't the right
answer to the right question for Facebook's purposes.

That decis= ion isn't an indictment of Cassandra's capability; it's
conf= irmation that Cassandra isn't everything to everyone. But we already knew that. :-)

--
David Strauss
=A0 | = david@fourkitchens.com
=A0= | +1 512 577 5827 [mobile]
Four Kitchens
=A0 | http://fourkitchens.com
=A0 | +1 512 454 6659 [office]
=A0 | +1 512 870 8453 [direct]


--000325576002f6c4b4048ab7ef6c--