2022-03-18
1911
#redux
Esteban Herrera
518
Mar 18, 2022 ⋅ 6 min read

Understanding Redux Saga: From action creators to sagas

Esteban Herrera Family man. Java and JavaScript developer. Swift and VR/AR hobbyist. Like books, movies, and still trying many things. Find me at eherrera.net

Recent posts:

Can native web APIs replace custom components in 2025?

Learn how native web APIs such as dialog, details, and Popover bring accessibility, performance, and simplicity without custom components.

Daniel Schwarz
Sep 12, 2025 ⋅ 9 min read
too many tools: How to manage frontend tool overload

Too many tools: How to manage frontend tool overload

Read about how the growth of frontend development created so many tools, and how to manage tool overload within your team.

Shalitha Suranga
Sep 11, 2025 ⋅ 12 min read
shruti kapoor the modern ai stack

What you actually need to build and ship AI-powered apps in 2025

Discover what you actually need to build and ship AI-powered apps in 2025, with tips for which tools to choose and how to implement them.

Shruti Kapoor
Sep 10, 2025 ⋅ 10 min read
ai dev tool power rankings

AI dev tool power rankings & comparison [Sept 2025]

Compare the top AI development tools and models of September 2025. View updated rankings, feature breakdowns, and find the best fit for you.

Chizaram Ken
Sep 10, 2025 ⋅ 9 min read
View all posts

5 Replies to "Understanding Redux Saga: From action creators to sagas"

  1. “A middleware is a piece of code that is executed after an action is dispatched but before reaching the reducer”.
    It’s the opposite – first reducer, then saga

  2. Hi,
    Not sure if I am missing something here, but with just one, simple call to API what is the point of using SAGA, instead of simple Thunk ?

Leave a Reply