Re:Twitter's Storm (complex event processing system) is now ...
by aaronblohowiak on Monday September 19, 2011 @02:20PM
(#3014618)
Thank you for releasing such thorough documentation with your project; it is a great indicator of professionalism and passion. ^.^
Re:Twitter's Storm (complex event processing system) is now ...
by nathanmarz on Monday September 19, 2011 @02:34PM
(#3014684)
Thanks! Good documentation is a critical part of having a usable project, and that will always be a focus of Storm. If you have any feedback for how the documentation can be better, please let me know.
Re:Twitter's Storm (complex event processing system) is now ...
by tom_b on Monday September 19, 2011 @08:45PM
(#3015799)
Just to point out, Nathan will be speaking at the Clojure/Conj conference this year. Talking about Cascalog.
I have a schedule conflict this year :( but would recommend the conference to everyone - the first year was informative with contagious enthusiasm. The other speakers also look cool.
Re:Twitter's Storm (complex event processing system) is now ...
by pp13 on Monday September 19, 2011 @02:50PM
(#3014764)
Why did you guys go with clojure, instead of something maybe like scala?
Re:Twitter's Storm (complex event processing system) is now ...
by nathanmarz on Monday September 19, 2011 @02:51PM
(#3014767)
I've had a ton of success using Clojure with projects like Cascalog and ElephantDB. It's a phenomenal language.
Re:Twitter's Storm (complex event processing system) is now ...
by nathanmarz on Tuesday September 20, 2011 @11:55AM
(#3018046)
And one more resource... here are the slides from my launch presentation of Storm:
http://www.slideshare.net/nathanmarz/storm-distributed-and-f...
Re:Twitter's Storm (complex event processing system) is now ...
by zaph0d on Tuesday September 20, 2011 @12:23AM
(#3016265)
Nathan,
Congratulations on the awesome work, Storm looks really great.
A minor nit, I was looking at the code, and all the hanging parens make it look really sad :-(
Re:Twitter's Storm (complex event processing system) is now ...
by zaph0d on Tuesday September 20, 2011 @08:03AM
(#3017205)
Bah, why the downvote? I was pointing out a major Lisp convention.
Re:Twitter's Storm (complex event processing system) is now ...
by varworld on Monday September 19, 2011 @02:21PM
(#3014623)
How does Storm compare to Kafka?
Re:Twitter's Storm (complex event processing system) is now ...
by anand_nalya on Monday September 19, 2011 @11:05PM
(#3016095)
Hi nathan, how does this compare to S4?
Re:Twitter's Storm (complex event processing system) is now ...
by nathanmarz on Tuesday September 20, 2011 @12:24AM
(#3016269)
The biggest difference is that Storm guarantees that data will be processed, whereas S4 can lose data. I also think Storm is significantly easier to use.
I've written a lot of documentation on the wiki, which you can find here: https://github.com/nathanmarz/storm/wiki
There's a few companion projects to Storm. These are:
One-click deploy for Storm on EC2: https://github.com/nathanmarz/storm-deploy
Adapter to use Kestrel as a Spout within Storm: https://github.com/nathanmarz/storm-kestrel
Starter project with example topologies that you can run in local mode: https://github.com/nathanmarz/storm-starter
Feel free to ask me questions here or on Storm's mailing list ( http://groups.google.com/group/storm-user ), and I'll answer as best I can!