Slides and Videos from the Cassandra Summit 2010
Here are the slides and videos from the Cassandra Summit SF.
Jonathan Ellis (Riptano) @spyced
The State of Cassandra. (Slides / Video)
Brandon Williams (Riptano) @faltering
Cassandra Performance Tuning. (Slides / Video)
Stu Hood (Rackspace) @stuhood
Partners in Crime: Cassandra Analytics and ETL with Hadoop. (Slides / Video)
Eben Hewitt @ebenhewitt
Understanding the Cassandra Data Model. (Slides Video)
Gary Dusbabek (Rackspace)
Getting to know the Cassandra Code Base. (Slides / Video)
Ben Black @b6n
Cassandra Troubleshooting: out of the shadows. (Slides / Video)
Kelvin Kakugawa (Digg) @kelvin
Distributed Counters in Cassandra (Slides / Video)
Cliff Moon @moonpolysoft
Dealing with the Thrift API. (Slides forthcoming / Video)
Noah Silas (Mahalo) and John Watson (Mahalo)
Cassandra at Mahalo. (Video)
David Strauss @davidstrauss (Four Kitchens)
Scalable queuing with flexible service levels. (Video)
Nate McCall (Riptano)
Hector v2: The Second Version of the Popular High-Level Java Client for Apache Cassandra (Slides / Video)
Paul Querna (Cloudkick) @pquerna / Dan Di Spaltra (Cloudkick)
Cassandra at Cloudkick. (PDF)
Brandon Williams slides 404.
404 fixed, thanks.
I liked the talk on Queuing by David Strauss. Especially since I had blogged about Messaging and Storage just a week ago – http://javaforu.blogspot.com/2010/08/blurring-line-between-messaging-and.html
Great job!
Its really good to read re-summarized knowledge which were scattered to various blogs, webpages and mailing list threads.
First of all: thanks for putting together the summit and for doing a great job of publishing video and slides from it.
I think the talk by Cliff Moon (@moonpolysoft) was probably the most important one in the series because it deals with some of the pain points when dealing with Cassandra that everyone has to go through. It is important to articulate such issues even if it may not be pleasant. It is important because it has a very direct effect on uptake and thus the long-term viability of the Cassandra project.
I hope this inspires people to help out on the Hector project. As Nate McCall pointed out, their original focus was to look at the plumbing, but they have since realized that the APIs are more important than first assumed. The people who work on it are a positive force in the Cassandra community. Support and help them if you can. (I try at least in small ways; schedule permitting)
Column oriented databases suffer from confusing nomenclature and Cassandra in particular suffers from a lot of confusion around treatment of column families vs super column families. The ideas are *really* simple, but this simplicity is not reflected in the APIs.
I usually explain the Cassandra data model like this:
http://blog.borud.no/2010/07/cassandra-data-model-in-two-lines.html
…and given that (overly simplified) explanation, one would think that it would be possible to dream up some relatively trivial APIs that can reduce the immensity of bloat that occurs in Cassandra client code.