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. (23 Mar 2020) high CPU when there is little work to be done
  2. (21 Feb 2020) The self signed certificate that couldn’t
  3. (31 Jan 2020) The slow slowdown of large systems
  4. (07 Jun 2019) Printer out of paper and the RavenDB hang
  5. (18 Feb 2019) This data corruption bug requires 3 simultaneous race conditions
  6. (25 Dec 2018) Handled errors and the curse of recursive error handling
  7. (23 Nov 2018) The ARM is killing me
  8. (22 Feb 2018) The unavailable Linux server
  9. (06 Dec 2017) data corruption, a view from INSIDE the sausage
  10. (01 Dec 2017) The random high CPU
  11. (07 Aug 2017) 30% boost with a single line change
  12. (04 Aug 2017) The case of 99.99% percentile
  13. (02 Aug 2017) The lightly loaded trashing server
  14. (23 Aug 2016) The insidious cost of managed memory
  15. (05 Feb 2016) A null reference in our abstraction
  16. (27 Jan 2016) The Razor Suicide
  17. (13 Nov 2015) The case of the “it is slow on that machine (only)”
  18. (21 Oct 2015) The case of the slow index rebuild
  19. (22 Sep 2015) The case of the Unicode Poo
  20. (03 Sep 2015) The industry at large
  21. (01 Sep 2015) The case of the lying configuration file
  22. (31 Aug 2015) The case of the memory eater and high load
  23. (14 Aug 2015) The case of the man in the middle
  24. (05 Aug 2015) Reading the errors
  25. (29 Jul 2015) The evil licensing code
  26. (23 Jul 2015) The case of the native memory leak
  27. (16 Jul 2015) The case of the intransigent new database
  28. (13 Jul 2015) The case of the hung over server
  29. (09 Jul 2015) The case of the infected cluster