The example project already uses Store for two different modules that are managed separately and don't depend on each other. An application (in this example, "admin") can statically compose the state for the modules, and make them share the same Store. It works well, but it does not allow lazy loading.
This is because some machinery is necessary in the Store itself to make it possible to dynamically compose reducers in the store as lazy loading occurs.
There is work underway now (April 2017) to enhance Store with this feature. Once that ships, hopefully in May, this example could be updated to use it.
The example project already uses Store for two different modules that are managed separately and don't depend on each other. An application (in this example, "admin") can statically compose the state for the modules, and make them share the same Store. It works well, but it does not allow lazy loading.
This is because some machinery is necessary in the Store itself to make it possible to dynamically compose reducers in the store as lazy loading occurs.
There is work underway now (April 2017) to enhance Store with this feature. Once that ships, hopefully in May, this example could be updated to use it.