DevOps is the combination of cultural philosophies, practices, and tools that increases an organization’s ability to deliver applications and services at high velocity: evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes. This speed enables organizations to better serve their customers and compete more effectively in the market.
There are three primary practice areas that are usually discussed in the context of DevOps:
•Infrastructure Automation: creating systems, OS configs, and app deployments as code.
•Continuous Delivery: build, test, deploy your apps in a fast and automated manner.
•Site Reliability Engineering: operating systems; monitoring and orchestration, sure, but also designing for operability in the first place.
The different parts of DevOps are:
•DevOps Values: DevOps values are effectively captured in the Agile Manifesto – with perhaps one slight emendation to focus on the overall service or software fully delivered to the customer instead of simply “working software.” Some previous definitions of DevOps, like Alex Honor’s “People over Process over Tools,” echo basic Agile Manifesto statements and urge dev+ops collaboration.
•DevOps Principles: DevOps at the conceptual level is mainly just the widening of Agile’s principles to include systems and operations instead of stopping its concerns at code checkin.
•DevOps Methods: Some of the methods here are the same; you can use Scrum with operations, Kanban with operations, etc. (although usually with more focus on integrating ops with dev, QA, and product in the product teams). There are some more distinct methods, like Visible Ops-style change control and using the Incident Command System for incident response.
•DevOps Practices: Specific techniques used as part of implementing the above concepts and processes. Continuous integration and continuous deployment, using configuration management, metrics and monitoring schemes, a toolchain approach to tooling or using virtualization and cloud computing is a common practice used to accelerate change in the modern infrastructure world.
•DevOps Tools: Tools used in the commission of these principles. In the DevOps world there’s been an explosion of tools in release (jenkins, travis, teamcity), configuration management (puppet, chef, ansible, cfengine), orchestration (zookeeper, noah, mesos), monitoring, virtualization and containerization (AWS, OpenStack, vagrant, docker) and many more. While, as with Agile, it’s incorrect to say a tool is “a DevOps tool” in the sense that it will magically bring you DevOps, there are certainly specific tools being developed with the express goal of facilitating the above principles, methods, and practices, and a holistic understanding of DevOps should incorporate this layer.
Benefits of DevOps:
•Speed
•Rapid Delivery
•Reliability
•Scale
•Improved Collaboration
•Security
•Automation
•Improved Communications.
The following are DevOps best practices:
•Continuous Integration
•Continuous Delivery
•Microservices
•Infrastructure as Code
•Monitoring and Logging
•Communication and Collaboration
•Infrastructure Automation: creating systems, OS configs, and app deployments as code.
•Continuous Delivery: build, test, deploy your apps in a fast and automated manner.
•Site Reliability Engineering: operating systems; monitoring and orchestration, sure, but also designing for operability in the first place.
The different parts of DevOps are:
•DevOps Values: DevOps values are effectively captured in the Agile Manifesto – with perhaps one slight emendation to focus on the overall service or software fully delivered to the customer instead of simply “working software.” Some previous definitions of DevOps, like Alex Honor’s “People over Process over Tools,” echo basic Agile Manifesto statements and urge dev+ops collaboration.
•DevOps Principles: DevOps at the conceptual level is mainly just the widening of Agile’s principles to include systems and operations instead of stopping its concerns at code checkin.
•DevOps Methods: Some of the methods here are the same; you can use Scrum with operations, Kanban with operations, etc. (although usually with more focus on integrating ops with dev, QA, and product in the product teams). There are some more distinct methods, like Visible Ops-style change control and using the Incident Command System for incident response.
•DevOps Practices: Specific techniques used as part of implementing the above concepts and processes. Continuous integration and continuous deployment, using configuration management, metrics and monitoring schemes, a toolchain approach to tooling or using virtualization and cloud computing is a common practice used to accelerate change in the modern infrastructure world.
•DevOps Tools: Tools used in the commission of these principles. In the DevOps world there’s been an explosion of tools in release (jenkins, travis, teamcity), configuration management (puppet, chef, ansible, cfengine), orchestration (zookeeper, noah, mesos), monitoring, virtualization and containerization (AWS, OpenStack, vagrant, docker) and many more. While, as with Agile, it’s incorrect to say a tool is “a DevOps tool” in the sense that it will magically bring you DevOps, there are certainly specific tools being developed with the express goal of facilitating the above principles, methods, and practices, and a holistic understanding of DevOps should incorporate this layer.
Benefits of DevOps:
•Speed
•Rapid Delivery
•Reliability
•Scale
•Improved Collaboration
•Security
•Automation
•Improved Communications.
The following are DevOps best practices:
•Continuous Integration
•Continuous Delivery
•Microservices
•Infrastructure as Code
•Monitoring and Logging
•Communication and Collaboration
