yggdrasil v3.2.2 Yggdrasil.Subscriber.Adapter.RabbitMQ View Source

Yggdrasil subscriber adapter for RabbitMQ. The name of the channel should be a tuple with the name of the exchange and the routing key. The exchange should be a topic e.g:

Subscription to channel:

iex(1)> alias Yggdrasil.Channel
iex(2)> sub_channel = %Channel{
...(2)>   name: {"amq.topic", "r_key"},
...(2)>   adapter: Yggdrasil.Subscriber.Adapter.RabbitMQ
...(2)> }
iex(3)> Yggdrasil.subscribe(sub_channel)
:ok
iex(4)> flush()
{:Y_CONNECTED, %Channel{name: {"amq.topic", "r_key"}, (...)}}

Publishing message:

iex(5)> pub_channel = %Channel{
...(5)>   name: {"amp.topic", "r_key"},
...(5)>   adapter: Yggdrasil.Publisher.Adapter.RabbitMQ
...(5)> }
iex(6)> Yggdrasil.publish(pub_channel, "message")
:ok

Subscriber receiving message:

iex(7)> flush()
{:Y_EVENT, %Channel{name: {"amq.topic", "r_key"}, (...)}, "message"}

Instead of having sub_channel and pub_channel, the hibrid channel can be used. For the previous example we can do the following:

iex(1)> alias Yggdrasil.Channel
iex(2)> channel = %Channel{name: {"amq.topic", "r_key"}, adapter: :rabbitmq}
iex(3)> Yggdrasil.subscribe(channel)
:ok
iex(4)> flush()
{:Y_CONNECTED, %Channel{name: {"amq.topic", "r_key"}, (...)}}
iex(5)> Yggdrasil.publish(channel, "message")
:ok
iex(6)> flush()
{:Y_EVENT, %Channel{name: {"amq.topic", "r_key"}, (...)}, "message"}

Link to this section Summary

Functions

Starts a RabbitMQ distributor adapter in a channel with some distributor publisher and optionally GenServer options

Stops the RabbitMQ adapter with its pid

Link to this section Functions

Link to this function start_link(channel, publisher, options \\ []) View Source

Starts a RabbitMQ distributor adapter in a channel with some distributor publisher and optionally GenServer options.

Stops the RabbitMQ adapter with its pid.