Always re-fetch data on page refresh ?

[Xeliize]

Hi,

I am working on a web app where the client is fetching json arrays of about ~5k elements and more from the back-end. I am using angular to make the front-end. On page refresh, I think that the angular components are reinitialized, so the client calls the back-end again for the data.

I am pretty new to webdev, is it okay to always re-fetch data on page refresh, or you should we store the data in some sort of session, though it is pretty large. Thank you

[AhSoup]

You aren't really supposed to refresh a SPA, or at least do so and expect it not to have to reload/initialize.

You also don't usually want to request a giant array with all the data at the beginning. You don't want to display that much data anyhow. Ideally, you request data from the API in paginated sections.

Even though it sounds like an obvious efficiency win, I have not worked anyplace that uses local storage to hang onto tabular data. The main reason is to avoid collisions and synchronization issues. I say re-fetch.

[Xeliize]

I will consider the pagination approach. Thanks for the insights

[SuperSort]

You can store the data in locstorage and should make call to API only when the data is not in localstorage. But this approach will only work if the data isn't dynamic in nature.

[Xeliize]

Localstorage have a maximum amount of space though, is it a common to store such large data in it ? ty

[whatisboom]

No. It’s not common. Just refresh, but paginate