CircleCI Coveralls

A message queue framework, with support for middleware and multiple adapters.

Check out this slide deck for more info.


The package can be installed as:

  1. Add conduit to your list of dependencies in mix.exs:
def deps do
  [{:conduit, "~> 0.12"}]
  1. If you are explicitly stating which applications to start, ensure conduit is started before your application:
def application do
  [applications: [:conduit]]

Getting Started

Once conduit is added to your project, you can generate a broker. For example:

mix --adapter amqp
mix --adapter sqs

The Broker is responsible for describing how to setup your message queue routing, defining subscribers, publishers, and pipelines for subscribers and publishers.

See mix help for all the options that are available. For example, specifying the adapter to use.

Officially Supported Adapters

In the future more adapters will be supported.

Configuring the Broker Topology

MQ’s have queues which need to be setup and may involve other concepts as well, including exchanges and bindings. Conduit attemps to stay out of the way when you need to define these things because each MQ has a different opinion on what you need.

Because of that, you’ll need to looks at the specific adapter for what options are available.

Configuring a Subscriber

A subscriber is responsible for processing messages from a message queue. Typically, you’ll have one subscriber per queue. You can generate a subscriber by doing:

mix conduit.gen.subscriber user_created

See mix help conduit.gen.subscriber for all the options that are available.

You can find more information about configuring your subscriber in the adapter specific docs here:

Configuring a Publisher

A publisher is responsible for sending messages. You can find more information abount configuring publishers in the adapter specific docs here: