Redux & State Management
Welcome, champion! 🔥
You've mastered 0 of 72 lessons. Start your first lesson free — no signup needed.
About this course
Redux is a library for keeping an app's shared state in one store and changing it only through actions handled by reducers. Most Redux code written today uses Redux Toolkit, the official way to write Redux, together with the React-Redux hooks. This online Redux course on Abekus teaches that current style in React and TypeScript through short reading-card lessons, each followed by an MCQ quiz, all built on one running example: the cart and product catalogue of an online shop called ShopKart, with prices in rupees.
Who this Redux course is for
It is written for React developers and front-end freshers who meet Redux in a job, an existing codebase or an interview. You should already know React components, props and useState, and be able to read basic TypeScript. No earlier Redux experience is needed: the first lesson wires a small cart slice into a React app, and the core ideas of store, action, reducer and one-way data flow are named only after you have seen them work.
The course stays on Redux Toolkit 2.x, React-Redux 9.x and RTK Query. It does not teach React basics, Redux-Saga, redux-observable, MobX or Recoil, and it does not cover Next.js, React Native or server components. Redux DevTools is taught through what it records, the actions and state changes, not through screens.
How the lessons work
Each lesson is a short set of reading cards on one idea, usually with a few lines of TypeScript, followed by a quiz of multiple-choice questions. Lessons run from basics up. You start with the store, actions, reducers and the three core rules, then see dispatch, getState, subscribe and the middleware pipeline. After that come configureStore and createSlice with Immer drafts, the builder callback for extraReducers, the Provider, useSelector and useDispatch with typed hooks, and why some selectors cause extra re-renders. Later topics cover createSelector, normalised state with createEntityAdapter, createAsyncThunk and the listener middleware, RTK Query endpoints, cache tags and optimistic updates, and app structure, testing and debugging. You go at your own pace.
The same code is used throughout. The cart state is always { items: CartItem[] }, the slice is always named "cart" with actions such as itemAdded and quantityChanged, and the products API always has getProducts, getProduct and addProduct with the "Product" tag, so each lesson builds on the one before it.
MCQ practice vs video courses for Redux
Video courses on Udemy, Coursera or YouTube are a good fit if you want to watch an instructor build an app end to end. This course is built for a narrower job: reading a short explanation with real code and then checking straight away whether you can predict what it does. Redux has many ideas that look alike, such as mutating an Immer draft and returning new state, useSelector with an object and with a single value, createAsyncThunk and RTK Query, or providesTags and invalidatesTags, and the quickest way to find where you mix them up is to answer questions that make you choose. Many learners use both formats: a video for the overall build, and question practice for the rules that cause real bugs.
Common Redux mistakes
The course takes these on directly, because they still appear in tutorials and old codebases:
- Starting a new app with createStore and hand-written action types. configureStore and createSlice are the current way.
- Mutating state in a plain reducer. Only inside createSlice does Immer turn draft changes into a safe new state.
- Both mutating the draft and returning a new value in the same reducer. Do one or the other.
- Returning a new object or array from useSelector on every call, which makes the component re-render after every action.
- Writing extraReducers as an object. That syntax was removed in Redux Toolkit 2.0; use the builder callback.
- Putting every piece of state in Redux. Form input, local toggles and server data often belong in React state or a cache such as RTK Query.
Best way to learn Redux
Learn it on one small app and keep asking where each piece of state should live. Build the cart slice first, read it with a memoised selector, add a thunk for checkout, then move product data to RTK Query and watch what the cache does. The last part of the course works this way: it compares Redux with React Context and Zustand, RTK Query with createAsyncThunk and TanStack Query, sets out when local state, form state or a server cache is the better home, and applies the ideas to shopping cart state, an auth session, a product catalogue with RTK Query and undo history.