DevOps
Development and Operations
In short
DevOps is a set of practices and a culture that brings software development and IT operations together to deliver software faster and more reliably.
What is DevOps?
DevOps combines development (writing software) and operations (running it in production) into one shared way of working. Instead of developers handing finished code over to a separate operations team, the same team is responsible for building, testing, releasing, and monitoring the software.
In practice, DevOps relies heavily on automation. Teams use CI/CD pipelines to test and deploy every change, infrastructure as code to create servers and networks from version-controlled files, containers for consistent environments, and monitoring and alerting to spot problems quickly. The goal is small, frequent, low-risk releases instead of large, infrequent ones.
A useful analogy is a restaurant where the chefs also hear customer feedback directly, instead of passing plates through a wall and never seeing the diners. Shorter feedback loops lead to faster fixes and better results. The DORA metrics, such as deployment frequency and time to restore service, are a common way to measure how well DevOps practices are working.
DevOps is often mistaken for a job title or a specific tool, but it is primarily a culture and a set of practices. A DevOps engineer is someone who builds the automation and platforms that make those practices possible. Related terms include SRE (site reliability engineering), which applies software engineering to operations, and DevSecOps, which builds security into every stage.
Key takeaways
- DevOps unites development and operations into one shared responsibility.
- Automation is central: CI/CD, infrastructure as code, and monitoring.
- Small, frequent releases reduce risk and speed up feedback.
- It is a culture and set of practices, not a single tool or product.
Readers ask
Is DevOps a job or a methodology?
DevOps is primarily a culture and set of practices. The title DevOps engineer usually refers to someone who builds and maintains the automation, pipelines, and infrastructure that support those practices.
What is the difference between DevOps and Agile?
Agile focuses on how teams plan and build software in short iterations with frequent feedback. DevOps extends that idea beyond development to include releasing, operating, and monitoring software in production.
What is the difference between DevOps and SRE?
SRE (site reliability engineering) is one concrete way of putting DevOps ideas into practice, using software engineering to run operations and measurable reliability targets called SLOs. DevOps is the broader culture.
Often compared
See also
- CI/CDDevOps & Cloud, p. 9CI/CD is a set of automated practices that build, test, and release code changes frequently, so software can be delivered to users quickly and safely.
- DockerDevOps & Cloud, p. 17Docker is an open-source platform for packaging an application and everything it needs into a container that runs the same way on any machine.
- KubernetesDevOps & Cloud, p. 32Kubernetes is an open-source system that automates deploying, scaling, and managing containerized applications across a cluster of machines.
- GitVersion Control, p. 10Git is a free, open-source distributed version control system that tracks changes to files over time, so developers can collaborate and undo mistakes.
- MicroservicesSoftware Architecture, p. 27Microservices are an architectural style where an application is split into small, independently deployable services that communicate over a network.
- ServerlessDevOps & Cloud, p. 47Serverless is a cloud model in which the provider runs your code on demand, manages all the servers, scales automatically, and bills only for actual use.
Spotted a mistake or something missing on this page?Suggest an edit