Week 24: Redux Toolkit Finally Made Redux Feel Simple + Deep Dive into React Router Data Fetching

This week felt like a shift.

Not because I learned something completely new…
But because things that once felt complex started becoming simple.

I moved from classic Redux to Redux Toolkit, and at the same time, I started understanding React Router at a deeper level — especially how data fetching actually works.

---

From Redux Complexity to Redux Toolkit Simplicity

Before this week, Redux felt structured… but heavy.

For a single feature, I had to think about:

• action types
• action creators
• reducers
• store setup

It worked, but it didn’t feel efficient.

Then I started using Redux Toolkit.

And honestly… it changed how I see Redux.

---

The Moment Redux Toolkit Clicked

Two things made the biggest difference for me:

1️⃣ configureStore

Earlier, setting up a store required multiple functions.

Now it’s just:

• one clean configuration
• everything handled internally

No unnecessary setup.
No confusion.

---

2️⃣ createSlice

This was the biggest upgrade.

Instead of writing:

• action types
• action creators
• reducers

I can now define everything in one place.

That means:

👉 Less boilerplate
👉 Cleaner code
👉 Better structure

For the first time, Redux felt practical.

---

Middleware & Thunks — Real-World Logic

I continued working with Redux Thunk.

This helped me understand how Redux handles:

• API calls
• async logic
• delayed actions

Instead of putting everything inside components, I started moving logic into Redux.

This made my components:

👉 cleaner
👉 easier to manage

---

React Router — Not Just Navigation Anymore

This week I also went deeper into React Router.

Before, I used it only for navigation.

Now I started understanding:

👉 It’s not just routing
👉 It’s also about data flow

---

Understanding createBrowserRouter

Instead of defining routes in a simple way, I explored a more structured approach.

Routes now feel like:

• a configuration system
• not just components

This makes large applications easier to manage.

---

Data Fetching with React Router (Big Realization)

This was the most interesting part of the week.

Before:

I used to fetch data inside components using useEffect.

Now:

React Router allows fetching data before the component renders.

That means:

• better user experience
• cleaner components
• more predictable data flow

This felt like a more professional approach.

---

What Changed for Me This Week

Before Week 24:

Redux felt heavy.
Routing felt basic.

After Week 24:

Redux feels simpler and cleaner.
Routing feels more powerful and structured.

---

Key Takeaways

• Redux Toolkit reduces unnecessary complexity
• configureStore simplifies setup
• createSlice organizes everything in one place
• Thunks help handle real-world async logic
• React Router is more than just navigation
• Route-based data fetching improves architecture

---

Final Thoughts

This week wasn’t about learning more tools.

It was about learning better ways to use them.

That’s the difference.

And slowly, things are starting to connect.

---

If you're learning React and Redux, my advice:

Don’t just follow tutorials.

Try to understand:

• how data flows
• where logic should live
• how to structure things properly

That’s where real growth happens.