The focus of scaling a Flux architecture is on the information that stores produce, rather than the various components. This chapter started with a discussion on the common practices of other architectures that involve the constant creation and destruction of JavaScript components. This is done to free resources, but it comes at a cost—the potential for error. Next, we looked at the relatively static nature of Flux architectures, where components have a long life. They don't have to constantly create and destroy components, which means that there's less potential for issues.
Next, we covered the concept of scaling information. We did so by demonstrating that our JavaScript components and the connections between them were the least of our worries when it comes to scaling the architecture. The real challenge comes when there's a lot of data to process, and the data that enters the system is likely to grow much faster than the number of JavaScript components we have.
We closed the chapter...