Book Image

Enterprise DevOps for Architects

By : Jeroen Mulder
4 (1)
Book Image

Enterprise DevOps for Architects

4 (1)
By: Jeroen Mulder

Overview of this book

Digital transformation is the new paradigm in enterprises, but the big question remains: is the enterprise ready for transformation using native technology embedded in Agile/DevOps? With this book, you'll see how to design, implement, and integrate DevOps in the enterprise architecture while keeping the Ops team on board and remaining resilient. The focus of the book is not to introduce the hundreds of different tools that are available for implementing DevOps, but instead to show you how to create a successful DevOps architecture. This book provides an architectural overview of DevOps, AIOps, and DevSecOps – the three domains that drive and accelerate digital transformation. Complete with step-by-step explanations of essential concepts, practical examples, and self-assessment questions, this DevOps book will help you to successfully integrate DevOps into enterprise architecture. You'll learn what AIOps is and what value it can bring to an enterprise. Lastly, you will learn how to integrate security principles such as zero-trust and industry security frameworks into DevOps with DevSecOps. By the end of this DevOps book, you'll be able to develop robust DevOps architectures, know which toolsets you can use for your DevOps implementation, and have a deeper understanding of next-level DevOps by implementing Site Reliability Engineering (SRE).
Table of Contents (21 chapters)
1
Section 1: Architecting DevOps for Enterprises
7
Section 2: Creating the Shift Left with AIOps
13
Section 3: Bridging Security with DevSecOps

Creating an architecture for heuristic automation

First, let's get a definition of heuristic: in the literature, it is referred to as applying a solution to an issue without the aim of being the optimal solution, but sufficient to fix the immediate problem that was discovered. Trial and error would certainly match this definition. The Hungarian mathematician George Pólya used the term in his book, How to Solve It, first published in 1945. He provided some practical ways of solving problems.

One of his principles is commonly used in architecture applying ML: if you don't have a solution, assume that you have a solution and see what it does. Keep the good stuff and analyze the bits that didn't work well. Try the iterated solution again and learn from it. This is the base of heuristic automation. It uses heuristic learning that can be leveraged through AI that is able to recognize and learn from patterns. AI will use algorithms and automation – it constantly...