1□What is DevOps?oA cultural and professional movement that stresses communication, collaboration, andintegration between software developers and IT operations professionals whileautomating the process of software delivery and infrastructure changes. It aims atestablishing a culture and environment where building, testing, and releasing software,can happen rapidly, frequently, and more reliably.o"Imagine a world where product owners, Development, QA, IT Operations and Infosecwork together, not only to help each other, but also to ensure that the overallorganization succeeds. By working towards a common goal, they enable the fast flow ofplanned work into production, while achieving world-class stability, reliability, availabilityand security."UWhy is DevOps Important?oTo meet these changing conditions, culture, practices and automation must becomemore "continuous".UDevOps Performance:oHighly evolved organizations have consistently demonstrated higher performance acrossfour key software performance metrics.o"Organizations that are "good at DevOps" have strong identities, clear responsibilities,autonomy over their own function, and well-defined interaction paradigms andcommunication channels with other teams."LDevelopment frequency: Low: Monthly or less often. Mid: Between daily andweekly. High: On demand (whenever we want).□Lead time for changes: Low: Between a week and 6 months. Mid: Less than aweek. High: Less than an hour.□MTTR: Low: Less than a week. Mid: Less than a day. High: Less than an hour.LChange failure rate: Low: Less than 15%. Mid: Less than 15%. High: Less than15%.□DevOps Foundation:oWith DevOps, people across the IT organization, working together, enable fast flow,feedback, and continuous improvement of planned work into production, whileachieving quality, stability, reliability, availability, security, and team satisfaction.□Practices: Automation, Architecture, Continuous Integration, ContinuousDelivery/Deployment, Continuous Testing.□Culture: Safe, trusting, respectful, collaborative, data driven, continuousimprovement, shared accountabilities.oThe Three Ways: are DevOps patterns identified in both "The DevOps Handbook" as wellas "The Phoenix Project."□The first way: Systems thinking.□The second way: Amplify Feedback Loops.□The third way: Culture of Continual Experimentation and Learning.1.Continuous FlowPreview Mode
This document has 71 pages. Sign in to access the full document!