Domain-Based Architecture

Domain-Based Architecture sits at the heart of redux architecture in Redux. This guide walks through the concept step by step, with examples, a cheatsheet, and common mistakes to avoid.

Domain-Based Architecture Overview

Domain-Based Architecture lets you work with Redux in a way that stays clear, repeatable, and easy to scale. Instead of ad-hoc steps, you follow a pattern that other developers recognise immediately.

The key is to keep domain-based architecture focused and predictable. Start from the minimal example here, then add only the complexity your situation actually needs.

import { configureStore } from '@reduxjs/toolkit';
import { Provider } from 'react-redux';

const store = configureStore({ reducer: rootReducer });

function App() {
  return (
    <Provider store={store}>
      <Root />
    </Provider>
  );
}

A Provider makes the single Redux store available to every component in the tree.

Domain-Based Architecture Example

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

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

Redux Cheatsheet

Quick Redux Toolkit reference related to domain-based architecture.

Concept	Example	Purpose
Store	`configureStore({ reducer })`	Hold app state
Slice	`createSlice({ name, reducers })`	State + actions together
Read state	`useSelector((s) => s.x)`	Get data in components
Dispatch	`useDispatch()`	Send actions
Async	`createAsyncThunk(...)`	Handle side effects
Data fetching	`createApi(...)`	RTK Query endpoints
Derived data	`createSelector(...)`	Memoized computations

How Domain-Based Architecture Works in Redux

Domain-Based Architecture 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.

A Provider makes the single Redux store available to every component in the tree.

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 Domain-Based Architecture

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

Concern	Recommendation
Boilerplate	Use Redux Toolkit (createSlice)
Server data	Prefer RTK Query over manual thunks
Performance	Memoize selectors with createSelector
Types	Use typed useAppSelector/useAppDispatch hooks

Common Mistakes

Skipping edge cases and error handling when using domain-based architecture.
Not verifying the result of domain-based architecture before moving on.
Over-complicating domain-based architecture before you actually need the extra flexibility.
Ignoring documentation, which makes domain-based architecture hard for the next person to follow.

Key Takeaways

Domain-Based Architecture is a core part of working effectively with Redux.
Start small and keep domain-based architecture focused on a single goal.
Apply consistent patterns so domain-based architecture scales across your project.
Practise and document domain-based architecture to keep your workflow maintainable.

Pro Tip

When you get stuck on domain-based architecture, reduce it to the smallest example first — most Redux problems become obvious once the noise is gone.