Flux is about information architecture, first and foremost. This is the reason that Flux is a set of patterns instead of a framework implementation. When we design front-end architectures that scale, the specific implementation matters very little, relative to the design of the overall system. It's things like unidirectional data-flows and synchronous update rounds that have a lasting impact on the scalability of the system. In fact, Flux can be influential enough that it changes the way we develop our software.
In this chapter we'll look at the software development lifecycle through the lens of Flux. We'll open the chapter with a discussion on the open-ended possibilities with Flux implementations. Then we'll compare the types of development activities that take place at the beginning of a new Flux project with what happens with a maturing Flux project.
We'll also think about the concepts that make Flux appealing to begin with, and how...