Production postmortemThe industry at large

time to read 1 min | 100 words

The following is a really good study on real world production crashes:

Simple Testing Can Prevent Most Critical Failures:
An Analysis of Production Failures in Distributed
Data-Intensive Systems

It makes for fascinating reading, especially since the include the details of the root cause of some of the errors. I wasn’t sure whatever to cringe or sympathize Open-mouthed smile.

image

More posts in "Production postmortem" series:

  1. (06 Dec 2017) data corruption, a view from INSIDE the sausage
  2. (01 Dec 2017) The random high CPU
  3. (07 Aug 2017) 30% boost with a single line change
  4. (04 Aug 2017) The case of 99.99% percentile
  5. (02 Aug 2017) The lightly loaded trashing server
  6. (23 Aug 2016) The insidious cost of managed memory
  7. (05 Feb 2016) A null reference in our abstraction
  8. (27 Jan 2016) The Razor Suicide
  9. (13 Nov 2015) The case of the “it is slow on that machine (only)”
  10. (21 Oct 2015) The case of the slow index rebuild
  11. (22 Sep 2015) The case of the Unicode Poo
  12. (03 Sep 2015) The industry at large
  13. (01 Sep 2015) The case of the lying configuration file
  14. (31 Aug 2015) The case of the memory eater and high load
  15. (14 Aug 2015) The case of the man in the middle
  16. (05 Aug 2015) Reading the errors
  17. (29 Jul 2015) The evil licensing code
  18. (23 Jul 2015) The case of the native memory leak
  19. (16 Jul 2015) The case of the intransigent new database
  20. (13 Jul 2015) The case of the hung over server
  21. (09 Jul 2015) The case of the infected cluster