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

Working with RAD

So far, we discussed how DevOps breaks down silos between developers and operations and how it helps in speeding up the development of products, services, and systems. Implementing DevOps will increase the velocity of development, but DevOps in itself is merely a way of structuring planning of development. It helps in planning in iterations: starting with a minimal viable product (MVP) and then iterating improvements in next versions. DevOps is not about the development of code itself. We need a development methodology for writing the code, but that methodology should fit with DevOps. In this section, we will look at RAD.

Why does RAD fit to DevOps and the agile way of working? The main reason is that RAD is agile in itself. RAD starts with prototyping (the MVP) and then focuses on iterations. The emphasis is on the fulfillment of requirements, rather than on planning. It allows developers to realize quick improvements and adjustments during the development cycle...