title: Observer pattern vs Event Bus message approach
body: <p>I've been looking at MVC implementations and Event-bus closely. </p>
  
  <p>Why not use Event-bus instead of Observer Pattern to implement a MVC application? </p>
  
  <p>For example, lets say I have two classes <code>Model</code> and <code>View</code>, In typical observer pattern it would be:</p>
  
  <pre><code>public class Model implements Subject { ... }
  
  public class View implements Observer { ... }
  </code></pre>
  
  <p>Instead, what is the benefit/drawback of an approach using <a href="http://greenrobot.org/eventbus/" rel="nofollow noreferrer">green robot event bus</a> or any other Event-bus?</p>
  
  <p>It would be something like:</p>
  
  <pre><code>public class Model {
     private int field = 0; 
  
     void someFunctionNowTriggerStateChange() {
       this.field = field + 1;
       ...EventBus.getDefault().post(this); //pass itself as the event
     }
  }
  
  public class View {
  
    @Subscribe onModelUpdated(Model model) {
      updateTextLabel(model);
      //other model updates
    }   
  }
  </code></pre>
  
  <p>What are the issues (if any) of using the EventBus to implement MVC vs typical Observer?</p>