Ruby Messaging Patterns
summary
Demonstrates replacing many brittle HTTP endpoints with a middleman message bus using RabbitMQ (AMQP) and a simple EventMachine + ruby amqp worker, showing horizontal scale by adding workers and RabbitMQ’s automatic round robin load balancing. Proposes moving intra-app work to async queues to cut database I/O (enqueue valid objects in memory, process later), compares alternatives Resque on Redis and queue_classic (Postgres), and notes trade offs: single-point-of-failure mitigated by persistence, clustering, and added complexity.
AI-written summary · about
chapters (5)
related talks
41mDecouple all the things: Asynchronous messaging keeps it simple
36mDRb vs. RabbitMQ Showdown
30mQueue Based Architectures with AMQP
42mSynchronous Reads, Asynchronous Writes
30mEvented Autonomous Services in Ruby
22mRack-AMQP: Ditch HTTP Inside SOA!
45mAdvanced Eventmachine
30mAdvanced Multithreading in Ruby