Please remove me from the list. Thank you.
It's sad to see engineers ready to switch from one solution to another, simply because they hear rumors about Facebook or some other large website moving away from it. The part the really bothers me is how people were ready to look for an alternative solution before they even verified this rumor or even heard the reason behind the rumor.
I would love to hear more about data modeling with Cassandra. I have gather a lot of good information from reading various presentations by Benjamin Black, Jonathan Ellis and others. The most important piece of the puzzle is to understand how you intend to access the data and then model everything based upon that.
Richard L. Burton III
On Tue, Jul 6, 2010 at 9:21 AM, Avinash Lakshman <firstname.lastname@example.org> wrote:
FB Inbox Search still runs on Cassandra and will continue to do so. I should know since I maintain it :).
On Tue, Jul 6, 2010 at 3:34 AM, David Strauss <email@example.com> wrote:
On 2010-07-05 15:40, Eric Evans
> 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.':
> 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. :-)
| +1 512 577 5827 [mobile]
| +1 512 454 6659 [office]
| +1 512 870 8453 [direct]
-Richard L. Burton III