---
title: "#redux articles | Hashnode"
description: "Redux is a predictable state container for JavaScript apps. Read the latest #redux articles and tutorials on Hashnode."
url: "https://hashnode.com/tag/redux"
---

Tag

# #redux

1,534 posts · 18,959 followers

[CEDRIC DERUE](https://hashnode.com/@strongerbyai) · [4d ago](https://hashnode.com/posts/redux-architecture-for-blazor-predictable-state-for-applications-that-grow/6af5e11542259de58fcf93f6)

### [Redux Architecture for Blazor: Predictable State for Applications That Grow](https://strongerbyai.hashnode.dev/redux-architecture-for-blazor-predictable-state-for-applications-that-grow?utm_source=hashnode&utm_medium=feed)

From scattered state to a traceable flow: Fluxor, pure reducers and guardrails for AI agents

14 min read · [strongerbyai.hashnode.dev](https://strongerbyai.hashnode.dev/redux-architecture-for-blazor-predictable-state-for-applications-that-grow?utm_source=hashnode&utm_medium=feed)

[Aakib Shah Sayed](https://hashnode.com/@Skyz) · [Oct 13](https://hashnode.com/posts/migrating-a-legacy-redux-codebase-to-redux-toolkit-a-phased-plan-that-doesn-t-stop-feature-work/6acdd1d3864d5144cfdc8bc5)

### [Migrating a Legacy Redux Codebase to Redux Toolkit: A Phased Plan That Doesn't Stop Feature Work](https://blog.aakibshah.com.np/migrating-a-legacy-redux-codebase-to-redux-toolkit-a-phased-plan-that-doesn-t-stop-feature-work?utm_source=hashnode&utm_medium=feed)

A 6-phase plan for moving a legacy Redux app (createStore, connect, sagas, constants files) to Redux Toolkit without a rewrite or a feature freeze.

9 min read · [blog.aakibshah.com.np](https://blog.aakibshah.com.np/migrating-a-legacy-redux-codebase-to-redux-toolkit-a-phased-plan-that-doesn-t-stop-feature-work?utm_source=hashnode&utm_medium=feed)

[Aakib Shah Sayed](https://hashnode.com/@Skyz) · [Oct 13](https://hashnode.com/posts/the-complete-redux-handbook-2026-edition-redux-toolkit-best-practices-and-common-pitfalls/6acdcfca4fb942f2397a756b)

### [The Complete Redux Handbook (2026 Edition): Redux Toolkit, Best Practices and Common Pitfalls](https://blog.aakibshah.com.np/the-complete-redux-handbook-2026-edition-redux-toolkit-best-practices-and-common-pitfalls?utm_source=hashnode&utm_medium=feed)

A practical, Redux Toolkit-first guide to Redux in 2026: slices, async logic, RTK Query, selectors, Next.js, testing, and the mistakes that slow down.

10 min read · [blog.aakibshah.com.np](https://blog.aakibshah.com.np/the-complete-redux-handbook-2026-edition-redux-toolkit-best-practices-and-common-pitfalls?utm_source=hashnode&utm_medium=feed)

[SDuX Vault](https://hashnode.com/@sduxvault) · [Sep 17](https://hashnode.com/posts/chapter-4-add-and-edit-records-without-mixing-editor-state-with-shared-feature-state/6aac4fba184f4522dca51b09)

### [Chapter 4 — Add and Edit Records Without Mixing Editor State with Shared Feature State](https://sdux-vault.hashnode.dev/chapter-4-add-and-edit-records-without-mixing-editor-state-with-shared-feature-state?utm_source=hashnode&utm_medium=feed)

Separate temporary editor state from committed Feature State for safe add and edit flows.

7 min read · [sdux-vault.hashnode.dev](https://sdux-vault.hashnode.dev/chapter-4-add-and-edit-records-without-mixing-editor-state-with-shared-feature-state?utm_source=hashnode&utm_medium=feed)

[Shams Mukhtar](https://hashnode.com/@shamsmukhtar) · [Sep 13](https://hashnode.com/posts/redux-first-principles-evolution-react-typescript-bug-tracker/6aa67591848f1201e1a1898a)

### [Redux from First Principles: Architecture, Evolution, and a React TypeScript Bug Tracker](https://shamsmukhtar.hashnode.dev/redux-first-principles-evolution-react-typescript-bug-tracker?utm_source=hashnode&utm_medium=feed)

Trace Redux from Flux to Redux Toolkit, then understand actions, reducers, hooks, Observer, Mediator, Publish/Subscribe, and state transitions through one working application.

27 min read · [shamsmukhtar.hashnode.dev](https://shamsmukhtar.hashnode.dev/redux-first-principles-evolution-react-typescript-bug-tracker?utm_source=hashnode&utm_medium=feed)

[Jayesh Sojitra](https://hashnode.com/@jayeshsojitra) · [Sep 1](https://hashnode.com/posts/context-api-vs-redux-vs-zustand-when-to-use-each/6a96a08b190e428e7b752633)

### [Context API vs Redux vs Zustand: When to Use Each](https://jayesh-sojitra.hashnode.dev/context-api-vs-redux-vs-zustand-when-to-use-each?utm_source=hashnode&utm_medium=feed)

"Just use Context" and "you need Redux" are both wrong answers to the same question, depending on what you're actually trying to solve.

3 min read · [jayesh-sojitra.hashnode.dev](https://jayesh-sojitra.hashnode.dev/context-api-vs-redux-vs-zustand-when-to-use-each?utm_source=hashnode&utm_medium=feed)

[Subramanya M Rao](https://hashnode.com/@Subramanya11) · [Aug 24](https://hashnode.com/posts/why-we-rewrote-an-88-screen-legacy-react-native-app/6a8c29b9a40a647d09e897ee)

### [Why We Rewrote an 88-Screen Legacy React Native App](https://subramanyarao.hashnode.dev/why-we-rewrote-an-88-screen-legacy-react-native-app?utm_source=hashnode&utm_medium=feed)

How we decided whether a large React Native app needed patient repair or a new foundation—and turned years of technical debt into explicit migration rules.

14 min read · [subramanyarao.hashnode.dev](https://subramanyarao.hashnode.dev/why-we-rewrote-an-88-screen-legacy-react-native-app?utm_source=hashnode&utm_medium=feed)

[Blogs World](https://hashnode.com/@blogs-world) · [Aug 18](https://hashnode.com/posts/we-migrated-a-dashboard-from-context-to-redux-mid-project-here-s-what-the-postmortem-actually-said/6a8411fd284c139294b5cef9)

### [We migrated a dashboard from Context to Redux mid-project. Here's what the postmortem actually said.](https://ankitkhoiwal.hashnode.dev/we-migrated-a-dashboard-from-context-to-redux-mid-project-here-s-what-the-postmortem-actually-said?utm_source=hashnode&utm_medium=feed)

A real internal-dashboard migration, what we measured before deciding, and the one thing that didn't actually improve

7 min read · [ankitkhoiwal.hashnode.dev](https://ankitkhoiwal.hashnode.dev/we-migrated-a-dashboard-from-context-to-redux-mid-project-here-s-what-the-postmortem-actually-said?utm_source=hashnode&utm_medium=feed)

[SDuX Vault](https://hashnode.com/@sduxvault) · [Aug 6](https://hashnode.com/posts/state-updates-need-policy-not-more-middleware/6a74be9f977947439a6e5e54)

### [State Updates Need Policy, Not More Middleware](https://sdux-vault.hashnode.dev/state-updates-need-policy-not-more-middleware?utm_source=hashnode&utm_medium=feed)

Why execution authority belongs outside your Behaviors

8 min read · [sdux-vault.hashnode.dev](https://sdux-vault.hashnode.dev/state-updates-need-policy-not-more-middleware?utm_source=hashnode&utm_medium=feed)

[SDuX Vault](https://hashnode.com/@sduxvault) · [Jul 20](https://hashnode.com/posts/the-fluent-api-that-makes-state-interaction-predictable-by-design/6a5e251f7e7fcacc7b218bcc)

### [The Fluent API That Makes State Interaction Predictable by Design](https://sdux-vault.hashnode.dev/the-fluent-api-that-makes-state-interaction-predictable-by-design?utm_source=hashnode&utm_medium=feed)

The power is in the predictability of the interactions

6 min read · [sdux-vault.hashnode.dev](https://sdux-vault.hashnode.dev/the-fluent-api-that-makes-state-interaction-predictable-by-design?utm_source=hashnode&utm_medium=feed)
