Hello! I just published a book on Site Reliability Engineering.
https://www.amazon.com/dp/B09QNZC2LL
This book is a collection of 28 chapters on SRE concepts, such as observability, monitoring, Service Level Objectives (SLOs), alerting, resilience and debugging.
I adapted each chapter from blog posts I've written over the last 4 years.
Most of the chapters detailed concepts that I applied while working at $dayjob, so they are 100% proven in real business settings :)
------
Some info on the backstory. Last year I started writing a book on my software development methodology. I put in ~80 hours and am ~25% done. I began getting discouraged and I wanted the practice of actually shipping an entire book from start to finish. I took 28 blog posts and combined them to create this book. I put in ~20 hours editing the book myself. I'm really happy to have this experience and am looking forward to resuming my other book.
I used leanpub to generate the pdf and epubs. Leanpub has its own markdown flavor called markua. I was originally drawn to leanpub because it has a pretty popular tech listing website. I didn't actually list on leanpub because they only pay using paypal, so I listed on amazon KDP instead.
Thank you!
It would be nice to know how it compares to or fits in with the Google SRE books [1].
[1]: https://sre.google/books/