13.5 Where to go from here?

This is the last section of the last chapter of this book, and I’d be lying if I said it didn’t feel weird. It really does. For the last year or so, writing this book has been a sort of daily ritual to me. Forcing myself out of bed hours too early to keep pushing was hard, but it made this book possible. And now my Stockholm syndrome is kicking in and I’m finding myself wondering what I'm going to do with all this free time!

With a topic as broad as chaos engineering, choosing what should go into the book and what was left out was objectively tricky. My hope is that the 13 chapters give you just enough information, tools and motivation to help you continue your journey on making better software. At the same time, it’s been my goal to remove all fluff and only leave a thin layer of padding in the form of a few jokes and “rickrolls” (if you don’t know what that means, I know you haven’t run the code samples!). If you’d like to see some things that didn’t make it into the main part of the book, see Appendix C. And if you’re still hungry for more after that, head straight to Appendix D!

If you’re looking for a resource that’s updated more often than a book, check out https://github.com/dastergon/awesome-chaos-engineering. It’s a good list of chaos engineering resources in various shapes and forms.

If you’d like to hear more from me, ping me on LinkedIn (I love hearing people’s stories with CE) and subscribe to my newsletter at http://chaosengineering.news.

Like I mentioned before, the line between chaos engineering and other disciplines is a fine one. In my experience colouring outside of these lines from time to time tends to make for better craftsmanship. That’s why I’d encourage you to take a look at some of these:

  • SRE
  • The three books from Google (https://landing.google.com/sre/books/):
    • “Site Reliability Engineering” by Betsy Beyer, Chris Jones, Jennifer Petoff and Niall Richard Murphy
    • “The Site Reliability Workbook” by Betsy Beyer, Niall Richard Murphy, David K. Rensin, Kent Kawahara and Stephen Thorne
    • “Building Secure & Reliable Systems” by Heather Adkins, Betsy Beyer, Paul Blankinship, Ana Oprea, Piotr Lewandowski, Adam Stubblefield
  • System performance
    • “Systems Performance: Enterprise and the Cloud” by Brendan Gregg
    • “BPF Performance Tools” by Brendan Gregg
  • Linux kernel
    • “Linux Kernel Development” by Robert Love
    • “The Linux Programming Interface: A Linux and UNIX System Programming Handbook” by Michael Kerrisk
    • “Linux System Programming: Talking Directly to the Kernel and C Library” by Robert Love
  • Testing
    • “The Art of Software Testing” by Glenford J. Myers
  • Other topics to observe
    • Kubernetes
    • Prometheus, Grafana

There are also two chaos engineering conferences worth checking out:

Finally “Chaos Engineering: System Resiliency in Practice” by Casey Rosenthal and Nora Jones is a good complement to this read. Unlike this book, which is pretty technical, it covers more high-level stuff and also offers first-hand experience from people working at companies in different industries. Give it a read.

And with that, time to release you into the wild world of chaos engineering. Good luck and have fun!

results matching ""

    No results matching ""