Normalized State

Normalized State Overview

At its core, normalized state is about doing one thing well in Redux. Once you understand the pattern, you can apply it consistently across projects and teams.

Good normalized state pays off across the whole project: fewer surprises, easier collaboration, and smoother onboarding. The snippet below is a solid starting point.

import { createEntityAdapter, createSlice } from '@reduxjs/toolkit';

const todosAdapter = createEntityAdapter();

const todosSlice = createSlice({
  name: 'todos',
  initialState: todosAdapter.getInitialState(),
  reducers: {
    addTodo: todosAdapter.addOne,
    removeTodo: todosAdapter.removeOne,
  },
});

createEntityAdapter stores normalized collections with ready-made CRUD reducers and selectors.

Normalized State Example

const slice = createSlice({ name, initialState, reducers });
const store = configureStore({ reducer: { key: slice.reducer } });
// dispatch(slice.actions.something())

• Start from a minimal Normalized State example and grow it only as needed.
• Keep things explicit so Normalized State behaves the same for everyone on the team.
• Name things clearly so teammates understand your Normalized State at a glance.
• Verify Normalized State works as expected before relying on it in important work.

Redux Cheatsheet

Quick Redux Toolkit reference related to normalized state.

How Normalized State Works in Redux

Normalized State follows Redux's predictable data flow: components dispatch actions, reducers compute the next state from the previous state and the action, and subscribed components re-render.

createEntityAdapter stores normalized collections with ready-made CRUD reducers and selectors.

• State lives in a single, read-only store.
• Actions are the only way to describe a change.
• Reducers are pure functions that return the next state.
• Redux Toolkit removes most boilerplate with slices and thunks.

Practical Guidance for Normalized State

In modern apps, normalized state should use Redux Toolkit rather than hand-written Redux. Keep state minimal, colocate logic in slices, and use RTK Query for server data.

Common Mistakes

• Copying normalized state commands or snippets without understanding what each part does.
• Skipping edge cases and error handling when using normalized state.
• Not verifying the result of normalized state before moving on.
• Over-complicating normalized state before you actually need the extra flexibility.

Key Takeaways

• Normalized State is a core part of working effectively with Redux.
• Start small and keep normalized state focused on a single goal.
• Apply consistent patterns so normalized state scales across your project.
• Practise and document normalized state to keep your workflow maintainable.