mirror of
https://github.com/tiennm99/java-design-patterns.git
synced 2026-05-14 14:58:39 +00:00
Robert Volkmann
465a6871b2
* refactor: move tests of leader-followers into correct package * dep: remove version constraint for Mockito in acyclic-visitor * dep: remove version constraint for Mockito in caching * chore: cleanup mockito-core import on some POMs * dep: upgrade core.mocktio 3.5.6 to 4.5.1 "- org.mockito.Mockito#verifyZeroInteractions an alias of verifyNoMoreInteractions" https://github.com/mockito/mockito/commit/caf35b24e2764df0498469526ecb3e7ec68a0430
title, category, language, tags
| title | category | language | tags | |
|---|---|---|---|---|
| Flux | Structural | en |
|
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
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.