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

Defining the roadmap to NoOps

NoOps is not a leap of faith. As with DevOps and AIOps, any next step requires a plan and a roadmap. Using the principles of heuristic automation and AIOps, we can leverage automation for intelligent automation, collaborating with cloud-native automation, and automated application deployment in CI/CD pipelines.

The following figure shows how NoOps consists of three major components. These three components are the roadmap to get to a level of automation where dedicated operations are no longer required. DevOps teams are end-to-end responsible for the development, deployment, running, and maintenance of the code, supported by fully automated processes and AI:

Figure 10.3 – Components of NoOps

The end state is predictive automation using predictive analytics that analyzes current data to eventually make predictions for the future. It includes the following:

  • Scaling for future needs, for instance by analyzing...