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

Implementing quality measures

By now, it should be clear that everything in DevOps is about being continuous, which, in other words, means continuous deployment, continuous integration, continuous testing, and continuous quality engineering. DevOps projects constantly focus on quality at every stage of development and operations. It's different from traditional approaches where teams have a separate phase to fix issues. In DevOps, teams constantly measure the products and fix issues as soon as they occur. One of the six DevOps principles is continuous improvement, which refers to the feedback loop wherein products are improved in every iteration, but also to the DevOps process itself.

A common practice in IT projects was to have a fixing phase, something that Gerald Weinberg describes in his book Perfect Software and other illusions about testing. The fixing phase was put at the end of the development phase before software was handed over to operations. In DevOps, we don&apos...