~/talk

"Distributed stream processing in Ruby"

Talkat RubyC 2019 · 2019-09-14..09-15· [data-engineering, ruby]
links:none on file
slides:none on file

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

  1. 0:00Introduction to stream processing
  2. 2:58Batch vs stream processing
  3. 7:19Stream basics and terminology
  4. 15:27Processing streams in three ways
  5. 19:04Stream processing use cases
  6. 23:28Apache Storm architecture
  7. 29:24Storm in Ruby overview
  8. 30:55Real-world example tracking
  9. 37:03Email sentiment analysis pipeline
  10. 39:20Costs and infrastructure
  11. 40:02Alternatives to Apache Storm
  12. 41:07Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.