Meta

Tag: Flux

Introduction

In the first part of this article series I started to talk about "WHY?" using Flux. Using a simple form component as example I demonstrated, that we need to decide how our form data flows. I concluded the post, that the inherent way of how data flows in component based application can be quite cumbersome, especially if a complex component consists of a multi-layered component-hierarchy. Traditional data-binding (may it one-way, or two-way) leads to a chain of re-passing data down- and upwards the component tree. Extrapolating the given problem we can depict the problem in a more generic way.

Introduction

When I started a new project few months ago I opted for ReactJS. As I was new to the concepts behind React I decided not to choose the Flux architecture pattern, which is often mentioned together with ReactJS. Of course, I started to cross-read articles about Flux, but honestly I had difficulties to understand the great "WHY?".