"Distributed stream processing in Ruby"
summary
Shows how Apache Storm topologies are built from Ruby spouts and bolts, using a community Ruby gem, Kafka spouts and HTTP calls to back-end services. Presents two real pipelines: an interaction counter that sustains ~100k requests per minute with end-to-end persist under 1 ms, and an email-scoring pipeline that runs a ML model and issues alerts. Claims Storm can benchmark million tuples per second, cluster of 2 Nimbus 2 ZK 4 supervisors runs 25 topologies for <$1,000/month.
AI-written summary · about
chapters (12)
- 0:00Introduction to stream processing
- 2:58Batch vs stream processing
- 7:19Stream basics and terminology
- 15:27Processing streams in three ways
- 19:04Stream processing use cases
- 23:28Apache Storm architecture
- 29:24Storm in Ruby overview
- 30:55Real-world example tracking
- 37:03Email sentiment analysis pipeline
- 39:20Costs and infrastructure
- 40:02Alternatives to Apache Storm
- 41:07Q&A
related talks
37mStorm, a Distributed Real-time Data Processing System
45mRuby for the soul of Big Data nerds
35mReal Time Marketing with Kafka, Storm, Cassandra & Spark #bbuzz
36mReal Time Big Data Analytics with Kafka, Storm, HBase #bbuzz
31mHelp I need a stream processor - learning how to chose ...
26mBuilding Stream Processing Applications with Ruby & Meroxa
30mFive Challenges in Real-time Stream Processing and Five Solutions
41mThe Engineer's Guide to Streaming
