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

Summary

In this chapter, we discussed the concept of NoOps – no operations. We discovered that the term might be misleading, since NoOps doesn't mean that the enterprise will no longer need operations at all. NoOps is a concept that leverages automation to its maximum potential. By automating development, deployment, and operations, scarce IT talent can focus on new features, since NoOps will help them by identifying and solving issues in IT systems fast. We've learned that NoOps (like AIOps) uses AI and ML. But NoOps also means that enterprises will need to embrace the shift-left mentality.

We've also learned that NoOps requires a specific type of architecture for heuristic automation: applying iterative solutions, learning from these solutions, and continuously improving them. We also discussed the different components of heuristic automation. In the final section, we explored a possible roadmap from DevOps to NoOps. We concluded that we already have the...