Learning from the errors in the application

When we talk about software development, we have the certainty, at some point, that the software will fail. There are many variables that can make errors happen in an application. There may be extensive testing coverage and monitoring, but at some point, something will fail.

The first point is—do not be afraid to fail. Mistakes happen, but it is important is to keep a history of these errors. Tracking history is directly linked to how a failure is documented and how this documentation can be quickly recovered to assist in the recovery of production applications.

It may seem a bit old-fashioned to write documentation about crashes. However, up-to-date and well-written documentation is one of the ...

Get Microservice Patterns and Best Practices now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.