Hacker News Reader

Nice work!

Suggestion: A lot of requests going to the server when creating a resume. Use local storage for storing the data and send it to the server once when user clicks the save button.

View on HN

We are thinking of local storage. There were multiple challenges related to it. Sending all data at once would make save slower. and when you save some small change a lot of data would have to be resaved at once. By splitting the data save into chunks we thought would give best performance - user experience balance. We will rethink on this and get back to you. thank you for your time :)

There is overhead for every request, one large request is generally faster than several small ones of the same size.

You have to be smart to send the data that is changed or client side compression is another option.

by chunking data to be saved we dont have to send all the data at all. so when you are saving personal info your position related data is not sent to server. but we send all personal related data again to save. this we thought reduced lot of complexity on the backend and gave best user experience by reducing number of clicks for saving data.

Reply on news.ycombinator.com