In this section, well go over the common case for asynchronous behavior in Flux architectures—making API calls over the network. Then, we'll discuss some the implications of asynchronous behavior in the context of user interactivity and the Flux tools available to deal with them.
Flux architecture is for the frontend of web applications. That said, there's going to be a lot of network communication between some components of our architecture and the backend API. This is the common case for asynchronous behavior, not just in Flux, but in the majority of JavaScript applications. Therefore, this is where the emphasis should be when designing action creators that directly communicate asynchronously with these API endpoints. Here's what the most common communication paths look like in Flux applications:
The stores need to be populated with data, and this is the most common way to get data—by fetching it from the API. In fact, the user is likely going to...