You're reading from Enterprise DevOps for Architects Leverage AIOps and DevSecOps for secure digital transformation

Product type Paperback

Published in Nov 2021

Publisher Packt

ISBN-13 9781801812153

Length 288 pages

Edition 1st Edition

Languages

Python

Tools

Ansible

Concepts

DevOps

Authors (2):

Jeroen Mulder

View More author details

Table of Contents (21) Chapters

Preface

1. Section 1: Architecting DevOps for Enterprises

2. Chapter 1: Defining the Reference Architecture for Enterprise DevOps FREE CHAPTER

3. Chapter 2: Managing DevOps from Architecture

4. Chapter 3: Architecting for DevOps Quality

5. Chapter 4: Scaling DevOps

6. Chapter 5: Architecting Next-Level DevOps with SRE

7. Section 2: Creating the Shift Left with AIOps

8. Chapter 6: Defining Operations in Architecture

9. Chapter 7: Understanding the Impact of AI on DevOps

10. Chapter 8: Architecting AIOps

11. Chapter 9: Integrating AIOps in DevOps

12. Chapter 10: Making the Final Step to NoOps

13. Section 3: Bridging Security with DevSecOps

14. Chapter 11: Understanding Security in DevOps

15. Chapter 12: Architecting for DevSecOps

16. Chapter 13: Working with DevSecOps Using Industry Security Frameworks

17. Chapter 14: Integrating DevSecOps with DevOps

18. Chapter 15: Implementing Zero Trust Architecture

19. Assessments

20. Other Books You May Enjoy

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...