In large React/Next.js apps, Redux Toolkit starts to feel like an anti-pattern when most of your state is really server data. Libraries like React Query or SWR handle fetching, caching and syncing much better, so RTK just adds code you don’t need.

RTK still works great when you’ve got complex client-side logic — shared UI state, multi-step flows, or anything that has nothing to do with the backend.

Simple rule of thumb:

– server data → React Query/SWR

– complex UI logic → RTK

By the way, when I was working on a similar architecture, I got some help from a team at Red Rocket Software — here’s their main page: https://redrocket.software/. They also build custom React/Next.js solutions, so their input was actually pretty useful.