In this chapter, we took a detailed look at stores in Flux architectures, starting with the aspects that are most likely to change once we've moved on from the skeleton architecture phase. We then introduced the notion of generic stores, the idea being to reduce the amount of state that individual stores have to keep. The awkward part of generic stores are the dependencies that they introduce, and to deal with them, you learned how to use the dispatcher's waitFor() mechanism.
Dependencies between stores come in two varieties, data dependencies and UI dependencies, and you learned that UI dependencies are a critical part of any Flux architecture. Finally, we discussed some of the ways that stores can grow out of hand in terms of complexity, and what can be done about it. In the following chapter, we'll look at view components in Flux architectures.