title: EventBus use, memory and architecture
body: <p>I'm starting using EventBus in my app and it's really nice to use, it solve a lot of problems and simplify the code, and the propagation all over the app with all threads and everything is fantastic, but I'm feeling I maybe abusing of the use of events. </p>
  
  <p>For now everything is fine, I'm testing in powerful devices and the app response is really nice, but I have a lot of coding to do yet and I'm starting to question myself how will affect having too much events triggering all over the app. </p>
  
  <p>So the question is for anyone that have experience with that library if there is some problems with having a lot of events in my app, if there is some known memory issues related to the use of this events. I'm trying to use it wisely, but it's difficult not to include it a lot in your architecture because it's a really nice functionality. Anyway if you have something to say about the subject will be nice because I have a lot of coding to do and will be a problem have my architecture wrong and have to go back to make changes because some issues related to the events. </p>
  
  <p>PD. I'm talking about native Android app, with a lot of networking</p>
  
  <p>Thx</p>