slack notifications system

• 

  LavinMQ UI shows queues published by slack_notifications_producer

• 

  message in hr_queue

• 

  message in marketing_queue

• 

  message in support_queue

Inspiration

The need to use a combination of binding and routing keys to know the right queue to forward a message to.

What it does

Set up an exchange, queues, and bindings to route messages to appropriate queues in the slack_notification system.

How we built it

Set up NodeJS environment on VS Code editor.

• The notification system has three queues, one per Slack channel.
• Created a direct exchange slack_notifications and three queues: hr_queue, marketing_queue, and support_queue in the slack_notifications_producer.js file.
• Then bound each queue to the slack_notifications exchange using the corresponding binding keys: hr, marketing, and support respectively.
• Compiled slack_notifications_producer.js file.

Challenges we ran into

Incorporating multiple queues was a little tricky.

Accomplishments that we're proud of

Simulated a scenario where the producer publishes messages to the hr, marketing, and support queues.

What we learned

Learned about exchanges, bindings, and routing keys in LavinMQ.

What's next for slack notifications system

Will modify the consumer created in the first challenge to fit the requirements of the notification system.

Built With

• lavinmq
• node.js