Master Branch:

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!

The Rationale page explains what Storm is and why it was built. This presentation is also a good introduction to the project.

Storm has a website at storm.apache.org. Follow @stormprocessor on Twitter for updates on the project.

Documentation

Documentation and tutorials can be found on the Storm website.

Developers and contributors should also take a look at our Developer documentation.

Getting help

NOTE: The google groups account storm-user@googlegroups.com is now officially deprecated in favor of the Apache-hosted user/dev mailing lists.

Storm Users

Storm users should send messages and subscribe to user@storm.apache.org.

You can subscribe to this list by sending an email to user-subscribe@storm.apache.org. Likewise, you can cancel a subscription by sending an email to user-unsubscribe@storm.apache.org.

You can also browse the archives of the storm-user mailing list.

Storm Developers

Storm developers should send messages and subscribe to dev@storm.apache.org.

You can subscribe to this list by sending an email to dev-subscribe@storm.apache.org. Likewise, you can cancel a subscription by sending an email to dev-unsubscribe@storm.apache.org.

You can also browse the archives of the storm-dev mailing list.

Storm developers who would want to track the JIRA issues should subscribe to issues@storm.apache.org.

You can subscribe to this list by sending an email to issues-subscribe@storm.apache.org. Likewise, you can cancel a subscription by sending an email to issues-unsubscribe@storm.apache.org.

You can view the archives of the mailing list here.

Issue tracker

In case you want to raise a bug/feature or propose an idea, please use Apache Jira

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 user@storm.apache.org.

If you are building storm from source, developing new features, or otherwise hacking storm source code, then dev@storm.apache.org is more appropriate.

If you are committers and/or PMCs, or contributors looking for following up and participating development of Storm, then you would want to also subscribe issues@storm.apache.org in addition to dev@storm.apache.org.

What will happen with storm-user@googlegroups.com?

All existing messages will remain archived there, and can be accessed/searched here.

New messages sent to storm-user@googlegroups.com will either be rejected/bounced or replied to with a message to direct the email to the appropriate Apache-hosted group.

License

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

http://www.apache.org/licenses/LICENSE-2.0

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.

The LICENSE and NOTICE files cover the source distributions. The LICENSE-binary and NOTICE-binary files cover the binary distributions. The DEPENDENCY-LICENSES file lists the licenses of all dependencies of Storm, including those not packaged in the source or binary distributions, such as dependencies of optional connector modules.

Project lead

• Nathan Marz (@nathanmarz)

Committers

• 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)
• Kishor Patil (@kishorvpatil)
• Sriharsha Chintalapani(@harshach)
• Sean Zhong (@clockfly)
• Kyle Nusbaum (@knusbaum)
• Parth Brahmbhatt (@Parth-Brahmbhatt)
• Jungtaek Lim (@HeartSaVioR)
• Aaron Dossett (@dossett)
• Matthias J. Sax (@mjsax)
• Arun Mahadevan (@arunmahadevan)
• Boyang Jerry Peng (@jerrypeng)
• Zhuo Liu (@zhuoliu)
• Haohui Mai (@haohui)
• Sanket Chintapalli (@redsanket)
• Longda Feng (@longda)
• John Fang (@hustfxj)
• Abhishek Agarwal (@abhishekagarwal87)
• Satish Duggana (@satishd)
• Xin Wang (@vesense)
• Hugo da Cruz Louro (@hmcl)
• Stig Rohde Døssing (@srdo)
• Roshan Naik (@roshannaik)
• Ethan Li (@Ethanlm)
• Govind Menon (@govind)
• Aaron Gresch (@agresch)
• Rui Li (@ruili)
• Bipin Prasad (@bipinprasad)

Acknowledgements

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.