Flux: A modern way of doing MVC? by Leitner David and Thomas Eizinger

We will go back to the origins and goals of the legendary MVC pattern which was first introduced in Smalltalk-76. Given this knowledge, the differences to alternatives like MVP or MVVM are pointed out, and similarities to more recent approaches like FLUX become quite obvious. By exploring the main ideas behind these concepts, the consequences of uni-directional and bi-directional dataflows or the relation between transient state, pure transformations and a single source of truth become reasonable.
Upon a closer look, it becomes clear that these concepts for managing UI state are not limited to a specific kind of technology or framework. Rather, they are suited for different kinds of problems. In a nutshell, state management in complex applications can be a tedious task, but this talk will increase your ability to use the right tool for the job.

[GintsPolis]

You forgot about one arrow, from view to actions. That's when finishing to render some view, another action should take a place. Having actions go trough one dispatcher is also big advantage.