Thats a very comprehensive explanation. Thanks a lot. I'll give this a try now.

But how this function (https://github.com/erikras/react-redux-universal-hot-example/blob/214de0dfb47b6d494b30146dd9ea0aba51228fcc/src/redux/modules/info.js#L35) is getting the state value when called from server side (on page reload) here (https://github.com/erikras/react-redux-universal-hot-example/blob/214de0dfb47b6d494b30146dd9ea0aba51228fcc/src/containers/App/App.js#L20). I am trying check something similar and couldn't figure out what is missing.

Thanks Sidhant. I am just trying to figure out which part of code in erikras' example is responsible for syncing the store to session?

Hi Christopher, I am learning react universal rendering with redux. I am following https://github.com/erikras/react-redux-universal-hot-example . The differences in my architecture are, I am not using Ducks as in the example. I am also using isomorphic-fetch instead of superagent. And I am not using any promise middleware since fetch itself return promise to async connect. But I am facing a strange issue. I have a popup for sign in. And sign in handled on client side completely. After signing in I am storing tokens and sessions in redux state. But when I refresh the browser, all the values in redux state become null. All I want is to retain the sign in data on page reload (server rendering). Do not know if I could explain you properly. But I am feeling like there must be a missing link in the entire redux flow. Thanks in advance.

I have faced the same issue few months back. I preferred a ground up work rather than using an all-inclusive framework. This helps me understand the actual workflow. Here is a project which you can follow to understand. And here is a fork with updated packages and feathers-authentication .