I was asked a very interesting interview question today.
Lets assume you have a single page application running on n users computers as a dashboard and you updated the application, how does all of the clients receive and manage the updated assets without incurring a browser refresh.
The first problem to figure out is how do I know the application was updated?
- Polling the entry bundle asset
- Polling the Index.html and comparing hashes/versions
- Polling some custom tiny server text doc
- Dashboard websocket contains the version
- On acquisition of new data it contains version
- We don't update until a change of route
Now we have a version, we distinguish that the server version is
greater than ours. How do we acquire the new asset?
- We fetch or receive it via
AJAX, create a
scripttag and allow the DOM to parse it. This bundle would have to include updated assets or links to lazy-loading all other required assets & template changes.
- We fetch a
version difffile which tells us which files have changed, we then request those updated files.
What are some gotchas in any form of updating a SPA without a browser refresh?
- Removing existing variables could be a memory nightmare, especially since we don't have direct memory management.
- Mutating existing variables could be a management nightmare which could result in significant debugging issues if some parts of code were relying on old code that's no longer available for example.
- Attaching scripts with each update would require removing of older scripts for cleanup assuming the system was never refreshed for many years. We don't want the DOM to get too big and unwieldy.
- This makes the whole thing almost a moot point as we would thereunto almost incur the same load as an entire page refresh.
- If we didn't want to reacquire all data then it would need to be stored pristinely outside of the application in the case the application updates the data can remain unaltered and intact.
- What happens when the api actually updates to an incompatible version? This is usually something you never want to do, but sometimes it's necessary.
- In such cases it would make sense to change the resource name to not break existing clients that have yet to update their dashboards.
- We see that an updated client is beholden to an updated api release. These both should be done at the same time. Having a refresh could make the most sense.
- Before we rashly jump into a new version, we need to make sure that the user has saved any changes - or we decide that it's important to our ux to query the user whether they are ready or okay with updating the application.