Why DevOps?

1. The release are highly reliable, but not fast enough.
2. Disconnects between Development and Operations increase mistake and MTTR when issues occur(The Mean Time To Repair)

Reasons why DevOps in need?

1. Improve quality and performance of the applications.
2. Improve the end customer experience.
3. A greater need for simultaneous deployment across different platforms.
4. Pressures to release applications more quickly.

Shorter Cycles & higher Quality

1. Faster time to market
2. Lower failure rates
3. Shortened lead time
4. Faster MTTR(mean time to realize, recover, repair, remediate)

More change in release equates to more risk.(continuous delivery, continuous feedback, continuous innovation)

Always try to automate things that can be automated.

You develop it, you test it and you run it(Change the way how we do deployment.)

1. Release management
2. Automation

Seven key DevOps practice:

1. Configuration management
2. Release Management
3. Continuous Integration
4. Continuous Deployment
5. Infrastructure as Code
6. Test Automation
7. Application Performance Monitoring

Seven DevOps habits:

1. Team Autonomy and Enterprise Alignment
2. Rigorous Management of Technical Debt
3. Focus on Flow of Customer Value
4. Hypothesis Driven Development
5. Evidence Gathered in Production
6. Live Site Culture
7. Manage Infrastructure as Flexible Resource

(Release code always attach to infrastructure, make sure that the infrastructures are also checked into version control, when you need to modify something, you do it in an automated fashion and check it as code in version control system.)

DevOps Metrics:

1. Deployment frequency
2. Change lead time
3. Change fail rate(how often failure occurs when you push code)
4. Mean time to detect & repair ()