Up until this point in the book, we've relied on the reference implementation of the Flux dispatcher. There's nothing wrong with doing this—it's a functional piece of software, and the dispatcher doesn't have many moving parts. On the other hand, it is just a reference implementation of a larger idea—that actions need to be dispatched to stores, and store dependencies need to be managed.
We'll kick things off by talking about the abstract dispatcher interface that's required by Flux architectures. Next, we'll discuss some of the motivations behind implementing our own dispatcher. Finally, we'll devote the remainder of the chapter to implementing our own dispatcher module, and then improving our store components so that they're able to seamlessly interact with the new dispatcher.