Introduction to the

This book is the first complete guide to DevOps written by a software architect. It systematically explains how to apply DevOps practices in different scenarios, including operations and maintenance, deployment pipeline, monitoring, security auditing, and quality concerns. Finally, it introduces DevOps practices through three classic cases. Written by Len Bass et al., translated by Xu Feng et al. Intended audience: – Software Architect – Project Manager – Technical Manager

The main content

What is the conversation

Definition: DevOps is a set of practices that reduce the time from delivery of system changes to deployment to production while maintaining high quality. Key points:

  • Reduce the time between submission and value generation
  • High quality

Why the conversation

Problems solved:

  • The deployment speed is slow after development
  • Errors occur frequently after deployment
  • Development operation rights protection responsibility is unclear
  • Insufficient operation and maintenance capability

Objective: to improve product competitiveness, that is, to improve speed and ensure quality.

How do you practice DevOps

Basics: – Version control – Continuous Integration – Deployment Strategy – Architecture microserv – Monitor everything, including but not limited to failures, performance issues, measure user feedback, security

Team roles for DevOps: – Product Owner – Reliability Engineer (can be tester) – gatekeeper – DevOps engineer

Case introduced

  • How does Rafter’s Chris Williams practice two data center synchronization
  • How can a company immediately know about implementing devOps
  • How Atlassian is refactoring old services into a DevOPs-enabled microservices architecture isn’t detailed here, but check out the original book if you’re interested.

Enterprise vision

It’s going to be much broader

conclusion

– This is an introductory book to DevOPS for experienced technicians. – There are a lot of good stuff, but it is very demanding for the reader. – Finally, there are three examples to illustrate how DevOPS can be practiced. More importantly, devOPS requires a high level of organizational structure and culture, a point the author emphasizes many times.