This issue arise from discussion in #43 , the ideia is to discuss possible enhancement and priority of the current controllers and messages package. Should be good to have a self-contained message processing logic for both incoming and outgoing direction working with message providers according to each micro service. In such way, we can have a cleaner structure to enable/disable certain messages and allows to declare all the things related in a single per message class.
We can assess how much effort it can take, and after that define if doing for the up-coming release or maybe leave it for the next release.
It is just an ideia that seems to fit better with the current architecture right, please ally suggestions are welcome.
This issue arise from discussion in #43 , the ideia is to discuss possible enhancement and priority of the current
controllersandmessagespackage. Should be good to have a self-contained message processing logic for both incoming and outgoing direction working with message providers according to each micro service. In such way, we can have a cleaner structure to enable/disable certain messages and allows to declare all the things related in a single per message class.We can assess how much effort it can take, and after that define if doing for the up-coming release or maybe leave it for the next release.
It is just an ideia that seems to fit better with the current architecture right, please ally suggestions are welcome.