Website Crash

Question

User-305496339 posted

What is the best practice for handling website crashes during a CRUD operation. Thanks !

Answer 1

User753101303 posted

Hi,

This is a diagnosis or a design question ? Assuming the later a common approach is to wrap multiple changes inside a single transaction. It allows to do all changes or no change at all. If using Entity Framework it is done for you already by SaveChanges.

If you meant fixing a crash, you should first gather as much information as you can '(know sources being your logging system, the Windows event log or tracing failing requests at the IIS level and in some rare casses could go to taking a crash dump with diagnosing tools).

Or please be more explicit if it doesn't help.

Answer 2

User-305496339 posted

Thank You for your help. I should have been more specific but this is as you were explaining a design issue. I was wondering what if i wanted to save data that a user may have had inputted in form fields. So that if there is a crash when they log back in the data  form is displayed with the data entered as it was before the system crashed. Would I use cookies? Thanks ! Oh by the way this is a question that I was asked during an interview regarding how I would handle the website crashing.

Answer 3

User61956409 posted

Hi rkrex,

 

As PatriceSc said, normally logs can help us troubleshoot IIS or application issues, you can try to enable IIS and application logs to gather useful logs. This article explain how to troubleshoot IIS and ASP.NET errors viadiagnosing logs, please refer to it.

 

rkrex

if there is a crash when they log back in the data  form is displayed with the data entered as it was before the system crashed. Would I use cookies?

If you want to persist data that user entered before, as you mentioned, maintaining user inputs in cookie could be an approach. If possible, you can also try other approaches, such as localStorage etc.

 

With Regards,

Fei Han