Ruby Messaging Patterns
summary
Argues that inserting an intermediary message broker actually removes synchronous coupling: uses rabbit mq over AMQP with the ruby amqp gem and EventMachine to run workers that dequeue and process jobs, and shows alternatives — delayed_job, Q (Postgres pub/sub) and reddis/Resque — with tradeoffs. Demonstrates controllers that enqueue validated objects instead of saving, scales by adding worker processes, surfaces the real bottleneck (the database), and explains persistence vs. in‑memory queues and failure modes.
AI-written summary · about
chapters (6)
related talks
41mDecouple all the things: Asynchronous messaging keeps it simple
30mQueue Based Architectures with AMQP
01h 05mScaling Applications with RabbitMQ
03mBuilding a Distributed Data Ingestion System with RabbitMQ
30mEvented Autonomous Services in Ruby
46mReal-world Examples of Message Queue Usage: Insights from RabbitMQ
32mRabbitMQ in Real Life - Tips and Tricks
39mReal World RabbitMQ: Exploring Practical Applications