a POC of using same components, stores, action and dispatcher to form a big round ball of flux happiness.
Browser & backend all using the same code and using the same actions through a dispatcher to sync their state.
I wanted to see what's the extent of isomorphism possible to be accomplished with this architecture. I was expecting to hit a stone wall at some point and to realize that this can't be done for some obvious reason. It was a positive surprise to notice that this is actually possible, the implementation is fairly simple (although a bit mind bending) and the amount of environment conditionals remained almost nonexistent.
I have no idea if this could be applied to a real-world architecture and would definitely like to hear ideas about how it could be done, could or should I change something in the current implementation and what kind of applications would benefit from this kind of structure.
git clone [email protected]:rikukissa/isomorphic-flux-concept.git
cd isomorphic-flux-concept
npm install
npm start
open http://localhost:9001 in your browser
https://github.com/facebook/react/tree/master/examples/server-rendering
https://medium.com/node-js-javascript/working-without-frameworks-part-1-b948f281f782