Messaging API supporting acknowledgements and request-response

Build Status Code Climate


  • Inject the appropriate logger and set up connection parameters:
logger =
freddy =, host: 'localhost', port: 5672, user: 'guest', pass: 'guest')

Supported message queues

These message queues have been tested and are working with Freddy. Other queues can be added easily:

Delivering messages

Simple delivery

Send and forget

Sends a message to the given destination. If there is no consumer then the message stays in the queue until somebody consumes it.

  freddy.deliver(destination, message)

Expiring messages

Sends a message to the given destination. If nobody consumes the message in timeout seconds then the message is discarded. This is useful for showing notifications that must happen in a certain timeframe but where we don't really care if it reached the destination or not.

freddy.deliver(destination, message, timeout: 5)

Request delivery

Expiring messages

Sends a message to the given destination. Has a default timeout of 3 and discards the message from the queue if a response hasn't been returned in that time.

response = freddy.deliver_with_response(destination, message)

Persistant messages

Sends a message to the given destination. Keeps the message in the queue if a timeout occurs.

response = freddy.deliver_with_response(destination, message, timeout: 4, delete_on_timeout: false)


deliver_with_response raises an error if an error is returned. This can be handled by rescuing from Freddy::InvalidRequestError and Freddy::TimeoutError as:

  response = freddy.deliver_with_response 'Q', {}
  # ...
rescue Freddy::InvalidRequestError => e
  e.response # => { error: 'InvalidRequestError', message: 'Some error message' }
rescue Freddy::TimeoutError => e
  e.response # => { error: 'RequestTimeout', message: 'Timed out waiting for response' }

Responding to messages

freddy.respond_to destination do |message, msg_handler|
  # ...

The callback is called with 2 arguments

  • the parsed message (note that in the message all keys are symbolized)
  • the MessageHandler (described further down)

The MessageHandler

When responding to messages the MessageHandler is given as the second argument.

The following operations are supported:

  • responding with a successful response

    msg_handler.success(response = nil)
  • responding with an error response

    msg_handler.error(error: "Couldn't process message")

Tapping into messages

When it's necessary to receive messages but not consume them, consider tapping.

freddy.tap_into pattern do |message, destination|
  • destination refers to the destination that the message was sent to
  • Note that it is not possible to respond to the message while tapping.
  • When tapping the following wildcards are supported in the pattern :
    • # matching 0 or more words
    • * matching exactly one word


freddy.tap_into ""

receives messages that are delivered to ""

freddy.tap_into "somebody.*.love"

receives messages that are delivered to but doesn't receive messages delivered to

The ResponderHandler

When responding to a message or tapping the ResponderHandler is returned.

responder_handler = freddy.respond_to ....

The following operations are supported:

  • stop responding

  • delete the destination

    • Primary use case is in tests to not leave dangling destinations. It deletes the destination even if there are responders for the same destination in other parts of the system. Use with caution in production code.

Notes about concurrency

The underlying bunny implementation uses 1 responder thread by default. This means that if there is a time-consuming process or a sleep call in a responder then other responders will not receive messages concurrently. To resolve this problem freddy uses a thread pool for running concurrent responders. The thread pool is shared between tap_into and respond_to callbacks and the default size is 4. The thread pool size can be configured by passing the configuration option max_concurrency.

Note that while it is possible to use deliver_with_response inside a respond_to block, it is not possible to use another respond_to block inside a different respond_to block.

Note also that other configuration options for freddy users such as pool sizes for DB connections need to match or exceed max_concurrency to avoid running out of resources.

Read more from


freddy was originally written by Urmas Talimaa as part of SaleMove development team.

SaleMove Inc. 2012

freddy is maintained and funded by SaleMove, Inc.

The names and logos for SaleMove are trademarks of SaleMove, Inc.