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

Planning operations with a maturity model

In this section, we will look at a maturity model for IT operations. Then, we will learn how to apply this to the enterprise and get it to continuous operations. Finally, we'll learn how to get it ready so that it can be implemented by AIOps.

The basic operations maturity model looks as follows:

Figure 6.7 – Operations maturity model

The first level is sometimes referred to as chaotic. Processes are not documented here; operations are merely just firefighting. At this level, it's the tools that define how operations work, instead of having an architecture in place that also defines the toolset. Most enterprises have passed this level.

However, a lot of enterprises are stuck at the second level. This is the committed level, where processes are defined. Incident, problem change, and project management is in place, but the processes are only integrated in a very limited way. There's no...