cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian O'Neill" <b...@alumni.brown.edu>
Subject A Big Data Trifecta: Storm, Kafka and Cassandra
Date Sat, 04 Aug 2012 11:41:06 GMT
Philip,

I figured I would reply via blog post. =)
http://brianoneill.blogspot.com/2012/08/a-big-data-trifecta-storm-kafka-and.html

That blog post shows how we pieced together Kafka and Cassandra (via Storm).
With LinkedIn behind Kafka, it is well supported.  They use it in
production. (and most likely we will too =)

Let me know if you end up using it.  Thus far, I think it pairs nicely
with Cassandra, but we don't have it in production yet.

-brian

On Fri, Aug 3, 2012 at 3:41 PM, Milind Parikh <milindparikh@gmail.com> wrote:
> Kafka is relatively stable and has a active well-supported news-group as
> well.
>
> As discussed by Brian, you would be inverting the paradigm of store-process.
> Essentially in your original approach, you are storing the messages first
> and then processing them after the fact. In the Kafka model, you would
> process the messages as they come in.
>
> Since you are thinking about parallelism anyways, I trust that your
> processing paradigm is inherently paralleizable.
>
> Regards
> Milind
>
>
>
>
>
> On Fri, Aug 3, 2012 at 12:22 PM, Philip Nelson
> <philipomailbox-cass@yahoo.com> wrote:
>>
>> Brian -- thanks.
>>
>> > We were looking to do the same thing, but in the end decided
>> > to go with Kafka.
>> > Given your throughput requirements, Kafka might be a good
>> > option for you as well.
>>
>> This might be off-topic, so I'll keep it short. Kafka is reasonably
>> stable? Mature (I see it's in the Incubator)? Relative to Cassandra?
>>
>> Philip
>>
>>
>



-- 
Brian ONeill
Lead Architect, Health Market Science (http://healthmarketscience.com)
mobile:215.588.6024
blog: http://weblogs.java.net/blog/boneill42/
blog: http://brianoneill.blogspot.com/

Mime
View raw message