Redux vs. useContext: Navigating the State Management Maze

Redux vs. useContext: Navigating the State Management Maze

Every developer knows that the software engineering isn’t just about writing code. It’s about creating efficient, maintainable, and scalable systems. A critical part of that journey, especially in React, is the state management. With numerous tools and libraries available, the choices can often be way too much. Two most common players in this arena are Redux and useContext hook which is native to React. Both offer ways to manage global state, but which is right for your project? Let’s dive in and understand these tools better.

Understanding useContext Hook
At its heart, useContext is a React hook introduced in version 16.8 that allows you to use context without having to wrap your components in higher-order components. The main idea behind it is to share values between components without having to pass props down manually at every level.

Imagine you have an application theme (light or dark) that many components in your app need access to. Instead of prop-drilling the theme down multiple component levels, you can use useContext to provide and consume the theme easily.


import { createContext } from 'react';

// Create a Context for the theme
const ThemeContext = createContext();

export default ThemeContext;


import React, { useContext } from 'react';
import ThemeContext from '../contexts/ThemeContext';

function DisplayComponent() {
  const theme = useContext(ThemeContext);
  return <div>{theme}</div>;

export default DisplayComponent;


import React from 'react';
import ThemeContext from './contexts/ThemeContext';
import DisplayComponent from './components/DisplayComponent';

function App() {
  return (
    <ThemeContext.Provider value="dark">
      <DisplayComponent />

In this simple example, the DisplayComponent accesses the theme value directly from the context without needing to receive it as a prop.

Unraveling Redux
Redux, on the other hand, is an independent library for JavaScript apps that manages state with a single immutable object. Its popularity has grown, especially with React applications, due to its predictability and the tooling it offers, like time-travel debugging.

At the core of Redux is the principle that changes in your application trigger actions, which are processed by reducers to produce a new state. The application then re-renders based on this new state.

Please do consider the fact that this is a ultra-simplified example for Redux. A real life example for Redux will be way more complicated and best practices suggest splitting in separate files. We can handle how to use Redux in detail in another blog post.


function counterReducer(state = 0, action) {
  switch (action.type) {
    case 'INCREMENT'
      return state + 1;
    case 'DECREMENT':
      return state - 1;
      return state;

export default counterReducer;


import { createStore } from 'redux';
import counterReducer from './counterReducer';

// Create a Redux store 
const store = createStore(counterReducer);

export default store;


import store from './redux/store';

store.dispatch({ type: 'INCREMENT' });
console.log(store.getState());  // Output: 1

In this Redux example, we define a simple counter reducer that responds to INCREMENT and DECREMENT actions.

Comparing the Giants
While both Redux and useContext help in state management, their approaches are different. Redux centralizes the application’s state and manages it through actions and reducers. Its middleware, like redux-thunk or redux-saga, helps handle side-effects. In contrast, useContext is a part of React itself, providing a way to pass data through the component tree without manual prop-drilling.

For Redux, some of its shining points include its ability to handle large and complex application states, the stable developer tools it offers, and the rich ecosystem around it. However, it is not a magic-wound. Redux introduces a lot of boilerplate often requiring additional libraries for asynchronous actions. It can be too much for smaller applications. Furthermore, its learning curve is steep for beginners.

useContext, in its turn, brings simplicity to the table. It’s straightforward to set up. This makes it perfect for small to medium-sized applications or features where the global state isn’t very complex. Yet, it has its set of challenges. Without careful design, useContext can cause unnecessary re-renders in your application. It lacks the middleware capabilities of Redux, and managing larger, more complex states can get messy.

The battle between Redux and useContext doesn’t and won’t able to have a clear winner. Like many things in software development, the answer to “which is better?” is often “it depends.” Evaluate the size and complexity of your project, the skills of your development team, and the specific problems you’re trying to solve before choosing.

Suleyman Cabir Ataman, PhD

Architectural Design Patterns 1 – Layered (or Tiered) Pattern

Here in this first post of the blog, I want to also start with the first part of a series. Read more

MongoDB through C# – Using the Official Library

MongoDB is a popular NoSQL database, which means it doesn't use tables like traditional databases. Instead, it saves data as Read more

Redux vs. useContext: Navigating the State Management Maze

Every developer knows that the software engineering isn't just about writing code. It's about creating efficient, maintainable, and scalable systems. Read more

NextJS: Frontend Sneaking into Backend

As web-based applications become more sophisticated, frontend and backend lines gets blur. One such example of this change is NextJS. Read more

Sharing on social media:

Suleyman Cabir Ataman

Leave a Reply