As most of you know already, I enjoy writing technical (Azure related) books. So if you are wondering why it’s been quiet lately, there is a good reason for it.
Actually, I was writing on my 9th book, making it 9 books in 9 years straight, but something got in-between the writing process and publishing. It’s called US Visa regulations :). Beginning this year, January 5th actually, I relocated from Belgium to Redmond, WA for Microsoft Corp. The work Visa I’m on allows me to only work for Microsoft, which obviously makes sense. But that meant I had to stop my side-activity as a book author with Apress.
Knowing I was already halfway in the actual writing process, so spent about 6 months from ideation to realization, I didn’t just want to scrap the chapters I already had. My MTT colleague and good friend Unai Huete Beloki, fellow-Azure DevOps trainer in my former EMEA team at Microsoft, was willing to step in and take over the writing process.
He did an amazing job, actually revamping some of the chapters I already had, moving the outline (=chapter order) around a little bit, and added a huge amount of his own views and experiences into the material. Honestly, only about 20% of my original writing was left. So it really became HIS book, with just a little bit of me left in. Obviously, I still offered to do Technical Reviewing (which gets paid with a free printed copy of the book).
Let’s check out what the book is about…
In short, based on the title, it covers a lot of the best practices on how to architect, build and run Azure workloads, but adding a lot of DevOps automation into doing this. Which summarizes what Site Reliability Engineering is about. As an SRE engineer, you spend about 50% of your time on developing, and 50% on doing engineering work. Which could involve designing new workload architectures, monitoring and observing actual-running workloads, automating the deployments using template-based Infrastructure as Code, as well as DevOps CI/CD Pipelines.
By the end of this book, you’ll have gained the confidence to design high-available and reliable Azure solutions, based on Microsoft Azure Reference Architectures, Azure DevOps and GitHub guidelines, and understanding more about the role of Site Reliability Engineering and designing for reliability and resiliency.
Table of Contents
- Chapter 1: The Foundation of Site Reliability Engineering
- Chapter 2: Service-Level Management Definitions and Acronyms
- Chapter 3: Azure Well-Architected Framework (WAF)
- Chapter 4: Architecting Resilient Solutions in Azure
- Chapter 5: Automation to Enable SRE with GitHub Actions/Azure DevOps/Azure Automation
- Chapter 6: Monitoring As the Key to Knowledge
- Chapter 7: Efficiently Handle Incident Response and Blameless Postmortems
- Chapter 8: Azure Chaos Studio (Preview) and Azure Load Testing (Preview)
Good for +250 pages of deep-technical content on Azure, DevOps and SRE practices!
Feel free to reach out if you got any more questions on this book or its content. Unfortunately I don’t have access to discount codes or free copies, if that would be your first ask :). The book is available on Amazon as printed copy, downloadable PDF/Epub and on Kindle as well as on Apress/Springer own catalog.
I hope you enjoy reading this work, learn from it, and become better in your role as DevOps/SRE engineer.
Cheers!!
/Peter