**This is a cross-post from my newsletter, Fitness && Functions.
After my last email mentioning Redux middleware, reader David Davis asked me about how this works in a React/Redux application.
I know it’s 2018 and Redux is dead and OMG why aren’t you just using React Context or Apollo and blah blah blah, and while I certainly agree that a lot of what Redux does for you is getting implemented into React itself, I’m thinking some of the people who love to hate Redux may only hate it because they’ve been using it wrong.
It seems many have been sprinkling their business logic in reducers, components, and even actions. But this is a recipe for having hard-to-reason-about code.
Straight from the Redux Docs:
…actions are just plain objects
Reducers are just pure functions
The solution has been there all along, but I don’t think enough of us knew about it or really understood it: Redux Middleware.
[Redux Middleware] provides a third-party extension point between dispatching an action, and the moment it reaches the reducer.
This is where your business logic should go!
Over the next few emails, I’ll share some examples of how to get up and running with Redux Middleware, but in the meantime: does this make sense to you? If you’ve used / are using Redux, where does your business logic live?