orchestrate-side-effects/handle-side-effects

Use listener middleware for reactive action-based workflows and complex orchestration, while createAsyncThunk suits imperative data fetching. Redux Toolkit side-effect strategy depends on whether the logic needs proactive triggering or passive reaction to state changes.

The best way to handle asynchronous data fetching with Redux Toolkit is typically RTK Query, which provides built-in caching and data synchronization. For custom imperative server interactions, createAsyncThunk offers a structured approach to manage loading states.

createListenerMiddleware works by attaching subscribers to specific actions or state changes, allowing reactive updates in RTK. It intercepts dispatched actions to trigger queued side-effect logic, ensuring safe and testable asynchronous processing without blocking the main store.

You do not need RTK Query for all side-effect management in frontend applications. While ideal for data fetching, handwritten thunks or listener middleware are recommended for processing actions, orchestrating complex sequences, and handling reactive updates.

You can use handwritten thunks alongside listener middleware in the same Redux store. This combination allows developers to handle imperative logic with thunks while delegating reactive background tasks and action-driven orchestration to the listener.

Redux Toolkit side-effect logic fails to scale when imperative workflows are overused for reactive updates. Selecting the correct strategy, such as listener middleware for action reactions or RTK Query for caching, ensures reliable and testable asynchronous state management.