The Flux architecture creates some restrictions on communication between components. The main principle is that of ubiquitous actions. The application view layer responds to user actions by sending action objects to a Dispatcher. The Dispatcher's role is to send every action to subscribed stores. You can have many stores and each one can act differently in response to the user's action.
For instance, imagine you are building a cart-based application. A user can tap the screen to add some item to the cart, upon which the respective action is dispatched and your cart store reacts to it. Also, an analytics store may track that such an item has been added to the user's cart. Both react to the same action object and use the information as needed. In the end, the view layer is updated with the new state.
