Message bus via the background queue you're already using.
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
lib update version Apr 17, 2017
spec spec updates Jan 21, 2015
.gitignore make the specs copyable per adapter Jan 16, 2015
.rbenv-version further along Aug 7, 2013
.rspec spec order change Jan 8, 2015
.rvmrc renaming Jan 16, 2015
Gemfile use one worker for ease of extensibility Jan 20, 2015
MIT-LICENSE readme and license May 17, 2012
README.mdown adds rake tasks and read Feb 5, 2015
Rakefile remove resque Jan 16, 2015
queue-bus.gemspec renaming Jan 16, 2015


Queue Bus

This gem uses Redis and background queues that you are already using to allow simple asynchronous communication between apps.


To install, pick one of the adapters and add it to your Gemfile:

And add the appropriate tasks to your Rakefile:

require "resque_bus/tasks" # or sidekiq_bus/tasks


Application A can publish an event

# pick an adapter
require 'resque-bus' # (or other adapter)

# business logic
QueueBus.publish("user_created", "id" => 42, "first_name" => "John", "last_name" => "Smith")

# or do it later
QueueBus.publish_at(1.hour.from_now, "user_created", "id" => 42, "first_name" => "John", "last_name" => "Smith")

Application B is subscribed to events

# pick an adapter
require 'resque-bus' # (or other adapter)

# initializer
QueueBus.dispatch("app_b") do
  # processes event on app_b_default queue
  # subscribe is short-hand to subscribe to your 'default' queue and this block with process events with the name "user_created"
  subscribe "user_created" do |attributes|

  # processes event on app_b_critical queue
  # critical is short-hand to subscribe to your 'critical' queue and this block with process events with the name "user_paid"
  critical "user_paid" do |attributes|

  # you can pass any queue name you would like to process from as well IE: `banana "peeled" do |attributes|`

  # and regexes work as well. note that with the above configuration along with this regex,
  # the following as well as the corresponding block above would both be executed
  subscribe /^user_/ do |attributes|
    Metrics.record_user_action(attributes["bus_event_type"], attributes["id"])

  # the above all filter on just the event_type, but you can filter on anything
  # this would be _any_ event that has a user_id and the page value of homepage regardless of bus_event_type
  subscribe "my_key", { "user_id" => :present, "page" => "homepage"} do

Applications can also subscribe within classes using the provided Subscriber module.

class SimpleSubscriber
  include QueueBus::Subscriber
  subscribe :my_method

  def my_method(attributes)
    # heavy lifting

The following is equivalent to the original initializer and shows more options:

class OtherSubscriber
  include QueueBus::Subscriber
  application :app_b

  subscribe :user_created
  subscribe_queue :app_b_critical, :user_paid
  subscribe_queue :app_b_default, :user_action, :bus_event_type => /^user_/
  subscribe :homepage_method, :user_id => :present, :page => "homepage"

  def user_created(attributes)

  def user_paid(attributes)

  def user_action(attributes)
    Metrics.record_user_action(attributes["bus_event_type"], attributes["id"])

  def homepage_method

Note: This subscribes when this class is loaded, so it needs to be in your load or otherwise referenced/required during app initialization to work properly.


Each app needs to tell Redis about its subscriptions:

$ rake queuebus:subscribe

See the adapter project for detils on running the workers.

Local Mode

For development, a local mode is provided and is specified in the configuration.

# config
QueueBus.local_mode = :standalone
QueueBus.local_mode = :inline

Standalone mode does not require a separate resquebus:driver task to be running to process the incoming queue. Simply publishing to the bus will distribute the incoming events to the appropriate application specific queue. A separate resquebus:work task does still need to be run to process these events

Inline mode skips queue processing entirely and directly dispatches the event to the appropriate code block.

You can also say QueueBus.local_mode = :suppress to turn off publishing altogether. This can be helpful inside some sort of migration, for example.


  • Replace local modes with adapters
  • There are a few spots in the code with TODO notes
  • Make this not freak out in development without Redis or when Redis is down
  • We might not actually need to publish in tests
  • Add some rspec helpers for the apps to use: should_ post an event_publish or something along those lines