29 lines
954 B
Markdown
29 lines
954 B
Markdown
---
|
|
layout: pattern
|
|
title: Flux
|
|
folder: flux
|
|
permalink: /patterns/flux/
|
|
pumlid: 7SP14eCm20NGg-W13FlU1YFLE0GpyAazVZk-rPkRLSrDqdKwW14l8kUxx0r7hXdYzJA8eTIhKzEy6UnqyeUNJQBjjWm6n2seS_n3Ryql2UgJajxBoAu_
|
|
categories: Presentation Tier
|
|
tags:
|
|
- Java
|
|
- Difficulty-Intermediate
|
|
---
|
|
|
|
## Intent
|
|
Flux eschews MVC in favor of a unidirectional data flow. When a
|
|
user interacts with a view, the view propagates an action through a central
|
|
dispatcher, to the various stores that hold the application's data and business
|
|
logic, which updates all of the views that are affected.
|
|
|
|
|
|
|
|
## Applicability
|
|
Use the Flux pattern when
|
|
|
|
* you want to focus on creating explicit and understandable update paths for your application's data, which makes tracing changes during development simpler and makes bugs easier to track down and fix.
|
|
|
|
## Credits
|
|
|
|
* [Flux - Application architecture for building user interfaces](http://facebook.github.io/flux/)
|