Working with external systems always presents potential for future problems. Every time you reference the external system in your code, you introduce a new place for your code to fall apart when that external system changes or needs to be updated.
RabbitMQ is no different. It is an external system that you should isolate from your application. You should move your RabbitMQ code as far out and away from your real application code as possible. Doing this allows you to more easily change how your messages are sent, how they are received, and what code processes them.
In this episode, then, you'll learn how to isolate your RabbitMQ configuration from your ExpressJS application code. And you'll see what it takes to create custom objects that encapsulate your message sending and receiving, using a library on top of Wascally, called Rabbus.