| From | To | Note |
|---|---|---|
RabbitMQ ready-q queue (Notifier) |
RabbitMQ routed exchange (Transformers) |
If there are queues bounded to the RoutingKey generated by the Notifier |
| - | RabbitMQ routed-dl exchange |
If there the RoutingKey generated by the Notifier is unroutable |
Router Route is responsible for building the Routing Key of a message after it has been written in the Raw Data Table.
For the sake of the PoC, we decided that the routing key is generated from the database and the collection where the data has been inserted.
| Database | Collection | Routing Key |
|---|---|---|
| skidata | ortisei | skidata.ortisei |
| skidata | skidata | skidata.skidata |
Even if the rule is quite trivial, we decided to create a dedicated route anyway to foresee any future logic which could be more complex.
The generated routing key is then used to inform the correct Transformer(s) about the newly inserted data.