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

Understanding the paradigm shift to NoOps

In the previous chapters, we discussed the introduction of artificial intelligence (AI) and machine learning (ML) into operations and development. In Chapter 9, Integrating AIOps in DevOps, we learned how an enterprise can leverage AI and ML in DevOps pipelines. The reason to do this is to make a lot of manual tasks obsolete through intelligent automation. NoOps takes all of this one step further: automate IT systems completely so there's no need for operators to manually intervene in the systems. How far away are we from that paradigm shift? In addition, is it realistic? We will discuss that in this section.

To answer the last question: NoOps seems to be more of an ideal than a real practice. The discussion around NoOps was initiated through the idea that teams could actually automate a lot of processes in development, especially regarding the deployment of applications. This started with services being provided as Software as a Service...