java-design-patterns/flux/README.md

---
layout: pattern
title: Flux
folder: flux
permalink: /patterns/flux/
categories: Structural
tags:
 - 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](./etc/flux.png "Flux")

## 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/)
Work towards #56: Splitting up the README I did the job and splitted up the readme, hopefully everything was splitted correctly... 2015-08-13 23:54:40 +02:00			`---`
			`layout: pattern`
			`title: Flux`
			`folder: flux`
Work towards #56: Add permalink to every pattern This makes cleaner URLs thanks to jekyll 2015-08-15 18:03:05 +02:00			`permalink: /patterns/flux/`
https://github.com/iluwatar/java-design-patterns-web/issues/8 Update pattern categories and tags 2019-12-13 21:09:28 +02:00			`categories: Structural`
Categorize and tag all patterns #213 2015-12-28 15:52:44 +02:00			`tags:`
https://github.com/iluwatar/java-design-patterns-web/issues/8 Update pattern categories and tags 2019-12-13 21:09:28 +02:00			`- Decoupling`
Work towards #56: Splitting up the README I did the job and splitted up the readme, hopefully everything was splitted correctly... 2015-08-13 23:54:40 +02:00			`---`

Use headings instead of bold text in index.md #238 2016-01-03 21:14:30 +01:00			`## Intent`
			`Flux eschews MVC in favor of a unidirectional data flow. When a`
Work towards #56: Splitting up the README I did the job and splitted up the readme, hopefully everything was splitted correctly... 2015-08-13 23:54:40 +02:00			`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.`

#1113 Link uml-reverse-mapper created class diagrams to readme, where needed 2019-12-07 20:01:13 +02:00			`## Class diagram`
Work towards #56: Splitting up the README I did the job and splitted up the readme, hopefully everything was splitted correctly... 2015-08-13 23:54:40 +02:00			`![alt text](./etc/flux.png "Flux")`

Use headings instead of bold text in index.md #238 2016-01-03 21:14:30 +01:00			`## Applicability`
			`Use the Flux pattern when`
Work towards #56: Splitting up the README I did the job and splitted up the readme, hopefully everything was splitted correctly... 2015-08-13 23:54:40 +02:00
Work towards #56: Add permalink to every pattern This makes cleaner URLs thanks to jekyll 2015-08-15 18:03:05 +02:00			`* 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.`
Work on #226, moved pattern specific credits to respective pattern pages in website 2015-09-03 18:17:07 +05:30
Use headings instead of bold text in index.md #238 2016-01-03 21:14:30 +01:00			`## Credits`
Work on #226, moved pattern specific credits to respective pattern pages in website 2015-09-03 18:17:07 +05:30
			`* [Flux - Application architecture for building user interfaces](http://facebook.github.io/flux/)`