This chapter looked at Flux in the larger context of the software development life-cycle. Since Flux is a set of architectural patterns for us to follow, they're largely open to interpretation as far as implementation goes. At the beginning of a Flux project, the emphasis is on iteratively delivering pieces of a skeleton architecture. Once we have a mature application with several features, the focus shifts to managing complexity.
We then discussed the possibility that other areas of our technology stack might want to borrow ideas from Flux. Things like unidirectional data-flows mean that there's less chance of side-effects and that the system as a whole is more predictable. Finally, we closed the chapter with a look at how we could potentially compose larger applications out of separately installable features made out of Flux components.
I hope this book has been an enlightening read on Flux architecture. The goal wasn't necessarily to nail down the ideal Flux implementation–I don...