Break Your App Like a Server
Errors do not always happen from user initiated actions—different processes and tools can fail on the server. Your application may experience network disconnections between servers, database slowness or downtime, and crashed processes due to bugs or a large amount of work. It’s nearly impossible to consider everything that can go wrong in an application, so you often won’t realize that there is a problem with failure handling until it’s too late. You can simulate many types of problems locally and in staging environments before experiencing them in production.
In this section, we’ll test what happens to our application during database downtime and when different processes crash on the server. We’ll utilize the observer ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access