Sign up for a live Kubernetes or DevSecOps demo

Click here

DevOps Glossary

DevOps

What is DevOps?

DevOps is a collection of best practices and working methods for the software development process whose cumulative goal is to shorten the development life cycle and support practice such as continuous integration, continuous delivery and continuous deployment. In today's business environment, software development teams must develop the capability to deliver features and updates with a high rate of frequency, delivering short turn-around times while maintaining the stability of the production environment.

The name "DevOps" is a portmanteau of "Software Development" and "Information Technology Operations", sometimes known as IT Operations or IT Ops. Central to the DevOps culture and philosophy is the idea that features should be delivered by cross-functional product teams that are equipped to both develop and run their software features. This notion is captured by the common DevOps mantra: "You Build It, You Run It".

In the past, software developers would build a new feature, than "throw it over the wall" to IT operations, where IT Ops teams would then have to determine how to test, run, support and maintain the feature. In DevOps, a cross-functional product team is expected to manage features from conception to production with input from developers and IT Ops. This eliminates knowledge silos between software development and IT Ops teams and leads to faster releases with fewer bugs.

DevOps Culture vs DevOps Methods

DevOps is an extremely new way of working for software development teams, with the first global DevOps conference known as DevOpsDday hosted in 2009. Despite its growing popularity and adoption by some of the world's leading Fortune 500 and technology companies, there is still a lack of agreement within the software development community about what constitutes the DevOps methodology. Some of the commonly referenced best practices that make up DevOps are:

  • Continuous Integration/Delivery/Deployment
  • Agile Software Development
  • Microservices Application Architecture
  • Infrastructure-as-Code
  • Effective Logging and Monitoring

While other software development paradigms, such as Agile software development, have a manifesto that delineates the exact methodologies for working within the system, DevOps places a strong emphasis on workplace and team culture and the need to facilitate communication and eliminate knowledge silos throughout the development process. DevOps practitioners have identified several cultural factors that can predict DevOps success, such as:

  • Development and operations teams working together
  • Frequent communication and collaboration between software developers and IT Ops
  • Product teams assume full owner and responsibility over assigned features
  • Product teams implement quality insurance and security throughout the design and development process

Reducing friction between IT Operations teams and software developers is one of the most important cultural benefits of DevOps. The establishment of collaborating, cross-functional teams ensures that IT Ops and developers work together towards solutions that benefit the customer instead of point fingers at each other when problems arise.

Successful DevOps teams embrace a collaborative culture and take ownership of their work while leveraging industry-leading techniques and working methods, along with best-of-breed software tools, to achieve the common goal of quicker releases and updates in a fast-paced development environment.

Understanding the DevOps Tool Chain

DevOps is a set of best practices and a new paradigm for software development, but it is not a prescriptive solution for software development. As with Agile software development, DevOps prioritizes the interactions of people over processes and technology - but processes and software are still part of DevOps.

A tool chain is a set of programming tools used to create a software product. DevOps practitioners follow a seven-step process for effective software development that leverages software tools to optimize each stage of the process:

Plan

In the planning phase, DevOps teams work to establish the business and application requirements for a a product or feature. This includes activities like gather requirements, creating a release plan, establishing security policy and requirements and deciding what metrics will be used to measure performance. Teams may use a software requirements definition tool such as Atlassian or iRise during this phase.

Create

In the creating phase, DevOps teams build, code and configure the software application. Teams may use metrics to measure code quality and performance, build performance and other methods before marking the product or feature as a candidate for release. Popular tools during this phase include GitLab, GitHub and CFEngine.

Verify

The purpose of software verification is to manage the quality of feature deployments into production. This includes software testing and validation exercises such as acceptance and regression testing, security and vulnerability analysis, configuration testing and performance measurement. Test automation tools and static security analysis applications are used in this stage of the development life cycle.

Package

When a new feature has passed verification, it is ready for release. The final step is to package the release, also known as "staging" This includes practices such as package configuration and may involve an approval process that integrates feedback from managers or executives. Package management software applications such as JFrog's Artifactory and ProGet are used by DevOps teams to facilitate release staging and holding.

Release

Releasing a new software update or feature means deploying that feature into a production environment where it can be accessed by users. DevOps teams must coordinate their releases with other feature releases while ensuring that there are back-ups in place to restore the system if the release causes a system failure. Some DevOps teams may automate the process using scheduled or timed releases. The best known vendors of release management software include IBM, BMC Software and VMWare.

Configure

The software development process does not end with release to production, as additional configuration may be required to optimize performance. These activities can include application or data storage provisioning, network provisioning and general configuration of the release. DevOps teams use Infrastructure-as-Code tools and configuration automation to streamline this process, with notable tools such as Ansible, Chef and Otter.

Monitor

Once a release has been configured and optimized, it should be monitored for performance and security, and to understand its impact on end users. DevOps teams are responsible for monitoring the performance of IT infrastructure, measuring customer experience using pre-defined metrics and capturing production statistics to ensure the feature is functioning correctly. Sumo Logic provides a premium tool that leverages machine learning to help DevOps teams facilitate effective application monitoring in the production environment.

Optimize Your DevOps Tool Chain with Sumo Logic

Sumo Logic is the world's leading platform for DevSecOps, providing functionalities that empower software developers, IT security analysts and IT operators to deliver the best results throughout the software development process. With Sumo Logic, DevOps teams can proactively monitor applications in the production environment for bugs, quickly detect security threats with the latest threat intelligence and capture critical application performance metrics that drive effective business decision-making.