gaspersic/java-design-patterns
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
java-design-patterns/flux
History
Anurag Agarwal 670c4e43f3 Java 11 migrate 7 remaining f (#1115) 
* Moves facade to Java 11

* Moves factory-kit to Java 11

* Moves factory-method to Java 11

* Moves feature-toggle to Java 11

* Moves fluentinterface to Java 11

* Moves flux to Java 11

* Moves flyweight to Java 11

* Moves front-controller to Java 11

* Uses stream properly

* Resolves issues with ci
2019-12-22 14:41:19 +02:00
..
etc
#1113 Add uml-reverse-mapper plugin
2019-12-07 18:03:49 +02:00
src
Java 11 migrate 7 remaining f (#1115)
2019-12-22 14:41:19 +02:00
pom.xml
Issue 989 batch-2 (#1108)
2019-12-18 22:04:08 +02:00
README.md
https://github.com/iluwatar/java-design-patterns-web/issues/8 Update pattern categories and tags
2019-12-13 21:09:28 +02:00

README.md

layout, title, folder, permalink, categories, tags
layout title folder permalink categories tags
pattern Flux flux /patterns/flux/ Structural
Decoupling

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.

Class diagram

alt text

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