Very nice. Helped me understanding Storm better. To bad that the demo was in Java made everything more compicated. Its kind of obvious that the Strom was written in Clojure. The Java Api seams to be a rather thin layer ontop of the clojure version. I cant imagen that you would have the same serialization problems in clojure, Nathan would of have fixed this. It will probebly be fixed in the java layer soon enought.
Edit: "I cant imagen that you would have the same serialization problems in clojure, Nathan would of have fixed this." seams like the wrong formulation. I didn't want to criticize. I guessed that the problem was in the Java API witch probebly has less testing then the clojure version but it seams to be a design decision.
I definitely get the sense that Java is a first-class citizen in the Storm world, even though it's written in Clojure. There's also the fact that I know next to nothing about Clojure (although I love Scheme, so maybe this'd be a good time to pick it up), but I definitely wouldn't mind doing a video on Storm's multilang support for other languages that I do understand (like Python or Ruby).
As for the serialization problems, that's mostly just a lack of documentation :( There was no problem with it once I learned how to register a serializer with Storm.
The serialization system needs more documentation, which I'll work on tonight. There are good reasons for every decision that was made with serialization. The feedback from this screencast was invaluable.
I love how the action unfolds at the end, each show competing for most buzz across Twitter while the tweets are streaming by! Nice work on lining up the commentary with events from the Emmys!
Edit: "I cant imagen that you would have the same serialization problems in clojure, Nathan would of have fixed this." seams like the wrong formulation. I didn't want to criticize. I guessed that the problem was in the Java API witch probebly has less testing then the clojure version but it seams to be a design decision.