Currently Iquidus Explorer is a all-in-one package: The frontend nodeJS Web App that people can view to explore the BlockChain, and a backend Sync tool which does all the heavy lifting. With the enhancements of clustering (both via cpu and the possibility of using multiple systems) there's a need now to separate the two. The backend, with the introduction and soon deprecation of "use_rpc", we no longer need the explorer to be visible to the backends to do our syncing. So this opens up numerous possibilities like Multi-Coin functionality as well as building better, more diverse applications for the front end to function and grow.
A few benefits of removing the Sync from the Frontend:
No longer does the frontend need to use as many workers to stay alive. The sync never hits the simple express app, so more resources are dedicated to visitors of the site than being used for the syncing operation.
Syncing is now exponentially faster. Again, we're not adding an additional hop to the mix, we're going directly to the daemon and moving on.
Frontend applications can be coded out of any language without needing the old express app running. Some proof of concepts will be posted soon.
Currently Iquidus Explorer is a all-in-one package: The frontend nodeJS Web App that people can view to explore the BlockChain, and a backend Sync tool which does all the heavy lifting. With the enhancements of clustering (both via cpu and the possibility of using multiple systems) there's a need now to separate the two. The backend, with the introduction and soon deprecation of "use_rpc", we no longer need the explorer to be visible to the backends to do our syncing. So this opens up numerous possibilities like Multi-Coin functionality as well as building better, more diverse applications for the front end to function and grow.
A few benefits of removing the Sync from the Frontend: