Summary
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 ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access