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

Monitoring pipelines with AIOps

In this section, we will study AI-driven technology that will help developers in monitoring and improving their CI/CD pipelines. Let's recap on the principle of a pipeline first. A pipeline should be seen as a workflow: it guides code through a process where it's tested and eventually deployed to a platform. Following this process, code will be pushed to different levels in the promotion path: development, testing, acceptance, and production. This process can be automated.

At the start of this process, and thus the pipeline, there is a repository where the various components of systems are stored. Since everything is code, the repository will hold code for applications, infrastructure components, configuration templates, and scripts to launch APIs. While building a system through a pipeline, DevOps software will make sure that the appropriate components are pulled from the repository and compiled into packages that can be deployed. A common...