Flux Architecture by Adam Boduch

Author:Adam Boduch [Boduch, Adam]
Language: eng
Format: azw3, pdf
Publisher: Packt Publishing
Published: 2016-05-24T04:00:00+00:00

Chapter 8. Information Lifecycle

Any information system has a lifecycle. Individual components in these systems have their own lifecycles as well. Cumulatively, these can be easy to deal with or overwhelmingly difficult. In frontend JavaScript architectures, the tendency is toward the latter. The reason is simple, the lifecycles that our components go through, fundamentally alter the flow of information over time in ways that are close to impossible to predict.

This chapter is about the information life cycle in Flux architectures. Flux is different from other architectures in that it puts emphasis on scaling information instead of on JavaScript components. We'll begin exploring this theme with a look at the difficulties we've faced for years, using the typical component lifecycles found in modern JavaScript frameworks. Then, we'll contrast this approach with that of Flux, where high-level components are relatively static.

Next, we'll jump into the concept of scaling information and how this leads to more sane architectures that are much easier to maintain than alternative approaches. We'll close the chapter with a discussion on inactive stores—stores that aren't actively serving a view with data. Let's get to it.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.