As someone who's admittedly rather unfamiliar with Redux and its patterns, I never could quite figure out how it should scale properly. Pretty much all the examples I've seen consisted mostly of very simple apps (a counter appears to be the "classic" one).
I'm wondering how to scale this pattern properly for larger apps, in this case specifically, how I can deal with all the Effects I need to write a full-featured app?
For example, let's say I have an app with 4 tabs, each containing a navigation controller, that itself contains and a couple of child view controllers. Adding to this user/session handling (login/logout/register etc.). Each of these view controllers (20 or so) make network calls to different API endpoints to fetch their data and display it, I also need to deal with persistance on disk of a lot of the models, state restoration, etc.etc... My understanding is that each of these interactions (network calls, load/persist to disk etc.), in the context of ReCombine, should be an Effect... considering I have dozens of Effects (being fairly conservative here, hundreds is probably more accurate), and just the one global Store object where I can register them, should I just pass in a big list containing all the effects that these dozens of screens require when I initialize the store? Is there a better way to do this?
Looks like the way to mitigate this with reducers is to use the combineReducers
functionality, is there something similar for Effects?