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 ops in an event-driven architecture

Let's review the most important task of ops once more: keeping services up and running. To enable this, we have defined a number of processes that help manage systems. Incident and problem management are key processes; that is, in IT4IT terms, detect to correct. The issue is that incident management is almost by default reactive: an issue is detected and actions are triggered to find and fix the issue. In the next phase, typically in problem management, a deeper analysis is done, where solutions are designed to prevent the issue from happening again.

Event management is a component of operations. The challenge in a digital operating model is to orchestrate and automate these events across different IT systems and even platforms. The event-driven architecture addresses this and is actually the starting point of AIOps. We will discuss this in more detail in Chapter 8, Architecting AIOps.

The event-driven architecture was originally...