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:
- Add
conduitto your list of dependencies inmix.exs:
def deps do
[{:conduit, "~> 0.12"}]
end- If you are explicitly stating which applications to start, ensure
conduitis started before your application:
def application do
[applications: [:conduit]]
endOnce conduit is added to your project, you can generate a broker. For example:
mix conduit.gen.broker --adapter amqp
mix conduit.gen.broker --adapter sqsThe Broker is responsible for describing how to setup your message queue routing, defining subscribers, publishers, and pipelines for subscribers and publishers.
See mix help conduit.gen.broker for all the options that are available. For
example, specifying the adapter to use.
- AMQP 0-9-1 - ConduitAMQP
- SQS - ConduitSQS
In the future more adapters will be supported.
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.
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_createdSee 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:
- AMQP 0-9-1 - Subscribers
- SQS - Subscribers
A publisher is responsible for sending messages. You can find more information abount configuring publishers in the adapter specific docs here:
- AMQP 0-9-1 - Publishers
- SQS - Publishers