mknoszlig/storm-amqp-spout — explained in plain English
Analysis updated 2026-07-18 · repo last pushed 2012-08-16
Feed a RabbitMQ queue of user events or log entries directly into a Storm topology for real-time processing.
Consume sensor readings from an AMQP broker without writing custom queue-polling code.
Use the shared queue option in production to guarantee messages survive a processing crash and restart.
Use the exclusive queue option for quick experiments or one-off data analysis.
| mknoszlig/storm-amqp-spout | abhishek-kumar09/pmd | ahus1/cdt | |
|---|---|---|---|
| Language | Java | Java | Java |
| Last pushed | 2012-08-16 | 2020-11-15 | 2024-11-05 |
| Maintenance | Dormant | Dormant | Stale |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 4/5 | 3/5 | 3/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires a running AMQP broker and an existing Storm topology to plug the spout into.
A connector that feeds messages from an AMQP broker like RabbitMQ into Apache Storm so real-time data streams can be processed as they arrive.
Mainly Java. The stack also includes Java, Apache Storm, AMQP.
Dormant — no commits in 2+ years (last push 2012-08-16).
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.