This chapter focused on asynchronous action creators in Flux architectures. These are functions that need to dispatch actions, but before they can, they have to wait for some asynchronous resource to resolve. We looked at the synchronous update round concept, which is central to any Flux architecture. Then, we discussed how action creators encapsulate asynchronous behavior in such a way that they preserve the synchronous update rounds.
Network calls are the most common form of asynchronous communication in JavaScript applications, including Flux architectures. We covered the difference between these and other asynchronous channels, and how promises can be used to bridge the gap between them. We also looked at how promises can be utilized by action creator functions to allow for the composition of more complex functionality.
In the next chapter, we'll take a deeper look at stores and everything they have to do to maintain consistent state in our Flux architectures.