nathanmarz
storm
Java2011–2014
nathanmarz / storm
storm
Distributed and fault-tolerant realtime computation: stream processing, continuous computation, distributed RPC, and more
22Distinct people
31Mentions
1Explicit recommenders
8.8KGitHub stars
What to know before exploring
What it is
Distributed and fault-tolerant realtime computation: stream processing, continuous computation, distributed RPC, and more
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
The master node coordinates the Storm cluster. It distributed code around the cluster, monitors topologies, and reassigns any tasks that have failed. Check out the wiki for…
nathanmarz used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- nathanmarz/storm-starter · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year31 dated mentions
Observed mentions: 2011-09-19 16:01:59 UTC to 2014-06-01 03:03:00 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2011 | 2011-01-01 00:00:00 UTC | 2012-01-01 00:00:00 UTC | 10 | 1 | 9 |
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 16 | 2 | 14 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 1 | 1 | 0 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
IMPORTANT NOTE!!!
Storm has Moved to Apache. The official Storm git repository is now hosted by Apache, and is mirrored on github here:
https://github.com/apache/incubator-storm
Contributing
Source code contributions can be submitted either by sumitting a pull request or by creating an issue in JIRA and attaching patches.
Migrating Git Repos from nathanmarz/storm to apache/incubator-storm
If you have an existing fork/clone of nathanmarz/storm, you can migrate to apache/incubator-storm by doing the following:
Create a new fork of apache/incubator-storm
Point your existing clone to the new fork:
git remote remove origin
git remote add origin git@github.com:username/incubator-storm.git
Issue Tracking
The official issue tracker for Storm is Apache JIRA:
https://issues.apache.org/jira/browse/STORM
User Mailing List
Storm users should send messages and subscribe to user@storm.incubator.apache.org.
You can subscribe to this list by sending an email to user-subscribe@storm.incubator.apache.org. Likewise, you can cancel a subscription by sending an email to user-unsubscribe@storm.incubator.apache.org.
You can view the archives of the mailing list here.
Developer Mailing List
Storm developers should send messages and subscribe to dev@storm.incubator.apache.org.
You can subscribe to this list by sending an email to dev-subscribe@storm.incubator.apache.org. Likewise, you can cancel a subscription by sending an email to dev-unsubscribe@storm.incubator.apache.org.
You can view the archives of the mailing list here.
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.incubator.org.
If you are building storm from source, developing new features, or otherwise hacking storm source code, then dev@storm.incubator.apache.org is more appropriate.
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.
Read the full README on GitHubWhat Hacker News says
31 sourcesHere's the root wiki:
https://github.com/nathanmarz/storm/wiki
Here's the system architecture:
https://github.com/nathanmarz/storm/wiki/Concepts
Here's non JVM languages (specifically python) for building spouts/bolts
https://github.com/nathanmarz/storm/wiki/Using-non-JVM-langu...
Here's an example project:
https://github.com/nathanmarz/storm-starter
In Ask HN: Fast, In-Memory, Distributed data analysis and machine learning?> Programs written in Hancock work by analyzing data as it flows into a data warehouse. That differentiates the language from traditional data-mining applications which tend to look for patterns in static databases.
Seems like Clojure and Storm:
http://pseudofish.com/storm-a-real-time-hadoop-like-system-i...
http://www.ibm.com/developerworks/library/os-twitterstorm/
http://www.infoq.com/presentations/Zolodeck
https://github.com/nathanmarz/storm/wiki/Rationale
In AT&T Invents Programming Language for Mass Surveillance (2007)When I saw the project name, the first thing I thought of was: https://github.com/nathanmarz/storm
In A command line tool to manage your ssh connectionsOne of the more commercially successful figures in the Clojure world. Early employee of a YC company (Backtype) with a successful exit to Twitter.
[1] http://www.crunchbase.com/company/backtype
[2] https://github.com/nathanmarz/storm
In Leaving Twitter- On the backend, for the realtime Twitter data analysis, Tweitgeist uses Redstorm which is a JRuby DSL & integration to the Storm engine.
https://github.com/colinsurprenant/redstorm
https://github.com/nathanmarz/storm
- Redis is used as a queue server.
- On the frontend side: Node.js, CoffeeScript, JavaScript, Bootstrap, jQuery, D3.js
Basically, Node serves a very simple API, everything else is in the browser.
... and please don't be too hard on the UI design, I basically suck with UI :P
In Realtime top hashtags on Twitter with Storm + JRuby + CoffeeScript + D3.jsI believe this is the problem that Storm was supposed to solve ( https://github.com/nathanmarz/storm ). Or Amazon's SWF ( http://aws.amazon.com/swf/ ). They work in the case where you can define the flow between all of the tasks.
In Asynchronous Processing in Web Apps, Part 1: A Database Is Not a QueueStorm : a Realtime Computation System Similar to Hadoop
30 points · Open discussionActually transactional topologies are superseded by Trident, which is much easier to use:
https://github.com/nathanmarz/storm/wiki/Trident-tutorial
Here's an explanation on how Trident achieves fully fault-tolerant, idempotent semantics:
https://github.com/nathanmarz/storm/wiki/Trident-state
In Storm's first birthdayStorm supports transactional topologies that can provide durability. They are dependent on a spout that is repeatable- where you can request the failed input again.
https://github.com/nathanmarz/storm/wiki/Transactional-topol...
In Storm's first birthdayRead the wiki:
"Guarantees no data loss: A realtime system must have strong guarantees about data being successfully processed. A system that drops data has a very limited set of use cases. Storm guarantees that every message will be processed, and this is in direct contrast with other systems like S4."
https://github.com/nathanmarz/storm/wiki/Rationale
In Storm's first birthdayOh easy questions:
The code itself is nice and clean, take a look yourself (chosen randomly) [1][2]
It's exciting because if you've ever done any real time processing of data streams at scale or even been daunted by the idea of it, and you read the wiki, it's clear storm is an exciting option. It does for Big Data Streams what Hadoop did for Big Data.
Kafka is interesting, but they don't really address similar use cases. They are more complimentary and in fact storm has a spout implementation for kafka[3].
[1] https://github.com/nathanmarz/storm/blob/master/src/clj/back...
[2] https://github.com/nathanmarz/storm/blob/master/src/jvm/back...
[3] https://github.com/nathanmarz/storm-contrib/tree/master/stor...
In Storm's first birthdayEven if you have no use for storm, I'd strongly suggest you check out the wiki on github and browse the source code. It is IMO the nicest, cleanest, most exciting OSS project out there.
https://github.com/nathanmarz/storm
In Storm's first birthdayStorm team develops new abstraction for real-time computing
2 points · Open discussionShowing the 15 most recent of 31 sources. Enable JavaScript to search and browse every indexed mention.