Thanks Ryan.
Ahmad Amireh

I’m curious how the CornFlux architecture would avoid the problems of store visibility and potential duplication. Am I right to assume that developers will still need to define Stores in separate files and then import and instantiate those stores in Container components? Depending on the structure of the project, it could still be very easy to lose visibility on what stores are already defined.

One benefit of Redux’s single store approach is that you can’t duplicate stores because there’s only one! At any point in time you can get complete visibility to the store by snapshotting its state. There is still potential for duplicating reducers and accidentally creating redundant parts of your state tree as the project grows, but I think that will always be a potential problem regardless of the Flux architecture you choose.

Like what you read? Give Travis Nuttall a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.