Presentation: TweetBeyond Flux - Scalable Frontend Architectures built upon Publish/Subscribe

The Flux architecture simplifies interface creation through a unidirectional data flow: the view simply renders a given data model and requests state changes through events.

In more complex applications however, this approach just moves model dependencies and state conflicts upwards, to the layer of stores. All stores are connected through a shared dispatcher, hurting encapsulation and reuse.

The publish/subscribe pattern generalizes on Flux: It connects selected components through configurable topics, enabling component reuse. I would like to introduce publish/subscribe by example and through a reference implementation, comparing it to Flux and its popular incarnations.