As you've seen so far in this chapter, Flux doesn't try to scale things that don't need to be scaled. For example, stores and views are often created just once during startup. Trying to clean these components repeatedly as the application changes state over time is simply error-prone. It's scaling the information that Flows through our Flux components that will knock our system over if we're not careful.
We'll start this section off with a look at how our Flux architectures can scale well on their own, without massive amounts of data entering the system. This also serves to illustrate the idea that these are in fact two separate problems—scaling the infrastructure of our Flux components versus scaling the volume of data that our architecture is able to process. Then, we'll discuss the topic of designing our user interfaces for less information, to make the design process of scalable components straightforward. We'll explore the role of Flux actions when it comes time to...