Storm is a distributed realtime computation system. Similar to how Hadoop provides a set of general primitives for doing batch processing, Storm provides a set of general primitives for doing realtime computation. Storm is simple, can be used with any programming language, is used by many companies, and is a lot of fun to use!
Documentation and tutorials can be found on the Storm website.
Developers and contributors should also take a look at our Developer documentation.
NOTE: The google groups account email@example.com is now officially deprecated in favor of the Apache-hosted user/dev mailing lists.
Storm users should send messages and subscribe to firstname.lastname@example.org.
You can subscribe to this list by sending an email to email@example.com. Likewise, you can cancel a subscription by sending an email to firstname.lastname@example.org.
You can also browse the archives of the storm-user mailing list.
Storm developers should send messages and subscribe to email@example.com.
You can subscribe to this list by sending an email to firstname.lastname@example.org. Likewise, you can cancel a subscription by sending an email to email@example.com.
You can also browse the archives of the storm-dev mailing list.
Which list should I send/subscribe to?
If you are using a pre-built binary distribution of Storm, then chances are you should send questions, comments, storm-related announcements, etc. to firstname.lastname@example.org.
If you are building storm from source, developing new features, or otherwise hacking storm source code, then email@example.com is more appropriate.
All existing messages will remain archived there, and can be accessed/searched here.
New messages sent to firstname.lastname@example.org will either be rejected/bounced or replied to with a message to direct the email to the appropriate Apache-hosted group.
You can also come to the #storm-user room on freenode. You can usually find a Storm developer there to help you out.
Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
- Nathan Marz (@nathanmarz)
- James Xu (@xumingming)
- Jason Jackson (@jason_j)
- Andy Feng (@anfeng)
- Flip Kromer (@mrflip)
- David Lao (@davidlao2k)
- P. Taylor Goetz (@ptgoetz)
- Derek Dagit (@d2r)
- Robert Evans (@revans2)
- Michael G. Noll (@miguno)
- Christopher Bertels (@bakkdoor)
- Michael Montano (@michaelmontano)
- Dennis Zhuang (@killme2008)
- Trevor Smith (@trevorsummerssmith)
- Ben Hughes (@schleyfox)
- Alexey Kachayev (@kachayev)
- Haitao Yao (@haitaoyao)
- Dan Dillinger (@ddillinger)
- Kang Xiao (@xiaokang)
- Gabriel Grant (@gabrielgrant)
- Travis Wellman (@travisfw)
- Kasper Madsen (@KasperMadsen)
- Michael Cetrulo (@git2samus)
- Thomas Jack (@tomo)
- Nicolas Yzet (@nicoo)
- Fabian Neumann (@hellp)
- Soren Macbeth (@sorenmacbeth)
- Ashley Brown (@ashleywbrown)
- Guanpeng Xu (@herberteuler)
- Vinod Chandru (@vinodc)
- Martin Kleppmann (@ept)
- Evan Chan (@velvia)
- Sjoerd Mulder (@sjoerdmulder)
- Yuta Okamoto (@okapies)
- Barry Hart (@barrywhart)
- Sergey Lukjanov (@Frostman)
- Ross Feinstein (@rnfein)
- Junichiro Takagi (@tjun)
- Bryan Peterson (@Lazyshot)
- Sam Ritchie (@sritchie)
- Stuart Anderson (@emblem)
- Lorcan Coyle (@lorcan)
- Andrew Olson (@noslowerdna)
- Gavin Li (@lyogavin)
- Tudor Scurtu (@tscurtu)
- Homer Strong (@strongh)
- Sean Melody (@srmelody)
- Jake Donham (@jaked)
- Ankit Toshniwal (@ankitoshniwal)
- Adam Lewis (@supercargo)
- Alexander Yerenkow (@yerenkow)
- Brenden Matthews (@brndnmtthws)
- Bryan Baugher (@bbaugher)
- Danijel Schiavuzzi (@dschiavu)
- David James (@xpe)
- David Losada (@tuxpiper)
- Francois Dang Ngoc (@darthbear)
- Gangrui Li (@davidlgr)
- John Gilmore (@jsgilmore)
- Julien Nioche (@jnioche)
- Kishor Patil (@kishorvpatil)
- Kyle Nusbaum (@knusbaum)
- Muneyuki Noguchi (@mnogu)
- Niels Basjes (@nielsbasjes)
- Padma Priya Chitturi (PadmaCh)
- Prabeesh K (@prabeesh)
- Sean Zhong (@clockfly)
- Sriharsha Chintalapani (@harshach)
- Srinivas Prasad Gumdelli (@srinivasgumdelli)
- Steven Phung (@stphung)
- Suresh Srinivas (@sureshms)
- thinker0 (@thinker0)
- Troy Ding (@troyding)
- Aaron Zimmerman (@aaronzimmerman)
- Albert Chu (@chu11)
YourKit is kindly supporting open source projects with its full-featured Java Profiler. YourKit, LLC is the creator of innovative and intelligent tools for profiling Java and .NET applications. Take a look at YourKit's leading software products: YourKit Java Profiler and YourKit .NET Profiler.