Given that the need to constantly create and destroy objects presents an opportunity for scaling issues, it seems that we should create and destroy as little as possible. It turns out that Flux architectures are different in this area in that much of the component infrastructure is static.
In this section, we'll look at what sets Flux apart from other architectures in this regard, starting with the singleton pattern that's used by many modules. Then, we'll compare the traditional MVC model approach to Flux stores. Lastly, we'll take a look at static view components and see if this is an idea worth pursuing in order to achieve scale.
As you've probably noticed by now, most of the modules we've worked with so far in this book have exported a single instance. The dispatcher exposes a single instance of the Dispatcher class from the Facebook Flux package. This is the singleton pattern in action.
The basic idea is that there's only one instance of a class...