We are in the process of converting a desktop application to a web application, and one of the challenges we are facing is the fact that when you make a change to the desktop application, it regularly persists those changes to memory in case of crashes (which were at one point frequent).

We had intended to shift that ideology away from constant saving to the user taking an action to save, to minimize impact and performance hits from constantly saving. However, the PO is having none of that and wants nearly constant saves whenever form data changes (I'm trying to get a better answer than that, because I don't want to send an update on every character).

How do "live saving" applications like google docs and similar handle this? I'm especially worried about performance because if we save too often, we're going to have a lot of saves firing off and overwhelm our services. Is there a design that will give us data integrity and performance?

  • 1
    It doesn't have to be on every character change. It can be on lost-focus, page-close, a timer or some other less-frequent event. The design is the one you create that meets your needs; there's no magic formula for saving, other than coming up with a sensible strategy and modeling. – Robert Harvey Nov 9 at 16:04
  • Have a look at stackoverflow.com/questions/43596477 – Robert Harvey Nov 9 at 16:14

Your Answer

 

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.