Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is it a bad design to have a global event bus in your application?
How to make sure you don’t end up with a tightly coupled set of components talking to each other all over the application?
Can you think of a mechanism/tools/library in Java world to enforce some discipline on it?
The problem with a global event bus i.e. an event bus which is accessible to every component (class or object) in your application, is that you have no control who will use the event bus.
If you are the sole developer or are working with a close knit team, it is possible to agree on the conditions when a component can use the event bus. Otherwise all bars are off.
Having said that, there should be a possibility to communicate with the event bus otherwise having it is pointless. By introducing an proxy for the eventbus who is responsible for the actual firing of the event, you can control who depends on the proxy.
By using dependency injection (via a framework like guice or hand-rolled) you can automatically provide the proxy state making the dependency on the eventbus explicit.