# MVC vs Flux

* For the most of the mvc framework, there is 2 ways data binding between model and view , also controllers can manipulate with each others to implement the logic 
* When the structure becomes more complex, it is really difficult to trace which part cause the change of model and the location of model that correspond to the view

![](https://1374779285-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFW3x2aqEO8GF2kr3VU%2F-MYfJJ91qFnPGz-2aIwz%2F-MYfJTWWg8VoWDMb6yFN%2Fimage.png?alt=media\&token=bf9fc317-63b9-4785-b89b-f9c555f2252e)

* Flux is a kind of one-way-data flow structure, store all of the data model into one place , and bind to corresponding view 

![](https://1374779285-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFW3x2aqEO8GF2kr3VU%2F-MYfJJ91qFnPGz-2aIwz%2F-MYfKRlo-pL51-AaoxTX%2Fimage.png?alt=media\&token=160cef65-ec49-4a03-8ccb-d868a7358291)

* So that it is easier to trace the logic and data model by making use of store and action
* Also , it is easier to perform a unit test