What is DevOps?
Table of contents
- Definition of DevOps
- The pillars of DevOps
- DevOps in one image
- What DevOps is not
- Why DevOps is essential
1 - Definition of DevOps
DevOps is a culture, a set of practices, and a philosophy that unifies software development (Dev) and IT operations (Ops).
Formal definition
DevOps is a set of practices that combines software development (Dev) and IT operations (Ops). Its goal is to shorten the development lifecycle and provide continuous delivery with high software quality.
The three dimensions of DevOps
| Dimension | Description |
|---|---|
| Culture | Collaboration between Dev and Ops teams |
| Practices | CI/CD, Infrastructure as Code, Monitoring |
| Tools | Git, Docker, Kubernetes, Jenkins, etc. |
DevOps is neither a tool nor a job title. It is above all a cultural shift in the way teams work together.
🔝 Back to table of contents
2 - The pillars of DevOps
The 5 core pillars (CALMS)
Detail of each pillar
Culture
DevOps culture is built on:
- Collaboration between developers and operations
- Shared responsibility for the product end to end
- Trust and open communication
- Continuous learning and the right to make mistakes
"You build it, you run it" - Werner Vogels, CTO of Amazon. This philosophy sums up the DevOps spirit: teams are responsible for their code in production.
Automation
Automation is at the heart of DevOps:
| Domain | Examples |
|---|---|
| Build | Maven, Gradle, npm |
| Tests | JUnit, Selenium, Jest |
| Deployment | Jenkins, GitLab CI, GitHub Actions |
| Infrastructure | Terraform, Ansible, CloudFormation |
| Monitoring | Prometheus, Grafana, ELK Stack |
Lean
Lean principles applied to development:
- Eliminate waste (waiting, handoffs)
- Deliver quickly
- Decide late, deliver early
- Empower teams
Measurement
What cannot be measured cannot be improved:
- MTTR (Mean Time To Recovery)
- Deployment frequency
- Change failure rate
- Lead time for changes
Sharing
- Accessible documentation
- Shared post-mortems
- Communities of practice
- Knowledge sharing sessions
🔝 Back to table of contents
3 - DevOps in one image
The DevOps cycle is an infinite loop (the ∞ symbol) representing continuous improvement.
🔝 Back to table of contents
4 - What DevOps is not
DevOps is often misunderstood. Here is what DevOps is NOT:
| Myth | Reality |
|---|---|
| A tool | DevOps is a culture, not a product |
| A job title | It is a methodology, not a single role |
| Just automation | Automation is a means, not an end |
| Only for startups | Applicable to organizations of any size |
| The end of Ops | Operations evolve, they do not disappear |
| Incompatible with security | DevSecOps integrates security into the cycle |
DevOps anti-patterns
Installing Jenkins does not make your organization a DevOps organization. Without a cultural shift, tools alone are not enough.
🔝 Back to table of contents
5 - Why DevOps is essential
The challenges of traditional development
The DevOps approach
Measurable benefits
According to the DORA State of DevOps report:
| Metric | Elite Organizations | Low Performers |
|---|---|---|
| Deployment frequency | Several times/day | Once/month to 6 months |
| Lead time | < 1 hour | 1-6 months |
| MTTR | < 1 hour | 1 week - 1 month |
| Failure rate | 0-15% | 46-60% |
High-performing DevOps organizations deploy 208 times more frequently than low-performing organizations.
Company examples
| Company | Before DevOps | After DevOps |
|---|---|---|
| Amazon | 1 deployment/week | 23,000 deployments/day |
| Netflix | Manual deployments | Thousands/day |
| Etsy | 2 deployments/week | 50+ deployments/day |
🔝 Back to table of contents
Key takeaways
- DevOps is a culture before it is a set of tools
- The 5 CALMS pillars: Culture, Automation, Lean, Measurement, Sharing
- DevOps aims to reduce time-to-market while improving quality
- Fast feedback is at the heart of the DevOps philosophy
- DevOps is not reserved for large tech companies