Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Separate RabbitMQClient and Messaging #66
We currently have business specific logic inside our RabbitMQ Client, that we're calling Messaging.
Messaging should have the po.et-specific things, and the start, publish and consume should be extracted to a RMQClient.
Messaging should receive an instance of the client as parameter or create it itself.
Once they are finally separate, avoid any logging in the RMQ Client or Messaging — communicating only via callbacks, throws and returns.