Let's look at the Flux architecture in a more formalized way. Here is a little diagram that shows how the simplified architecture looks:
Flux diagram from official documentation: https://github.com/facebook/flux
Each of the pieces in the preceding diagram has its own purpose in the circular chain:
- Dispatcher: The manager of what's happening in the application. This manages actions and provides them to registered callbacks. All actions need to pass through the Dispatcher. The Dispatcher must expose the register and unregister methods to register/unregister callbacks, and must expose the dispatch method, which dispatches actions.
- Stores: The application consists of multiple stores that register callback(s) in the Dispatcher. Each store needs to expose a public constructor method that accepts the Dispatcher argument. The constructor is responsible...