Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Enterprise DevOps for Architects

You're reading from  Enterprise DevOps for Architects

Product type Book
Published in Nov 2021
Publisher Packt
ISBN-13 9781801812153
Pages 288 pages
Edition 1st Edition
Languages
Concepts
Author (1):
Jeroen Mulder Jeroen Mulder
Profile icon Jeroen Mulder

Table of Contents (21) Chapters

Preface 1. Section 1: Architecting DevOps for Enterprises
2. Chapter 1: Defining the Reference Architecture for Enterprise DevOps 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

Integrating AIOps with service architecture

So far, we have looked at the logical and different components of AIOps. One of the main reasons to bring AI into operations is to relieve operators of a lot of manual tasks by proactively monitoring systems and even mitigating possible risks before they actually materialize. In other words, AIOps is invented to reduce what Site Reliability Engineering (SRE) calls toil. That's the whole point of implementing DevOps and AIOps: to reduce toil and create time to continuously design and build better systems.

But it's not only about the systems themselves. Enterprises also have processes to deliver services. That's the domain of the service architecture. Or, better and more precise: the technical service architecture. That includes the processes that are discussed in the following subsections.

Monitoring

This is not something that simply comes out of the box. On the contrary, architects need to define a monitoring architecture...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}