The Essential DevOps Terms You Need to Know

New to the world of DevOps and looking to get a handle on some key industry terms? Look no further. This quick list of essential DevOps terms will serve as a foundation from which you can appreciate industry tools and methodologies.


Precursor to Dupes; Agile is a software program improvement and, more broadly, commercial enterprise methodology that emphasizes short, iterative planning and improvement cycles to maximize change as tasks evolve. Break down and provide predictability and guidance.


DevOps (Development and Operations) is an enterprise software program improvement phrase used to suggest a type of agile relationship between development and IT operations. DevOps aims to enhance exchange and relationship by advocating high verbal exchange and collaboration between two commercial enterprise units.

Continuous Delivery

Continuous Delivery (CD) is a set of techniques and methods that completely eliminate waste from your software program manufacturing process, allowing for faster delivery of superior performance and consistency between your business enterprise and your customers. Creates a fast and positive feedback loop.

Continuous Integration

Continuous integration (CI) is an improvement practice that requires builders to integrate code into a common repository in different instances a day. Each check-in is then validated with an automated build, allowing groups to spot issues as quickly as possible.


Microservices are a graph pattern of software program structure, in which complex functions consist of small, neutral operations that each use language-agnostic APIs. These offerings are small, tightly coupled and focused on doing one small thing.

Release Orchestration

Release orchestration is the use of tools such as XL Release to control the release of a software program from the development phase to the actual software program launch.


Provisioning is the technique of creating new customer-ready structures (in a continuous delivery scenario, typically look at improvements or teams). Infrastructure is typically virtualized and instantiated on demand. Configuration of machines to installation running systems, middleware, etc. is handled by automated gadget configuration administration tools, which also verify that preferred configurations are maintained.

Configuration Management

A term for configuring and saving formal settings and functional attributes for a system. It consists of tools for device administration duties such as IT infrastructure automation.

Deployment Management

Planning the deployment management follow-up, managing the release movement to check and live the agenda and environment.

Test-Driven Development (TDD)

An improvement practice in which small checks are written before the code itself to validate the behavior of a piece of code. Initially the checks fail, and then the developer(s) must add code to make them succeed. Check out Xebia Labs' checking dashboard and analytics tool here.

Build Automation

Tools or frameworks that allow routine compilation of source code into releasable binaries. Usually consists of code-level units that try to make certain parts of the code behave as expected.

Unit Testing

Code level (ie, not requiring a fully hooked-up end-to-end device to run) Attempting to verify the behavior of the male or female parts of the code. Test-driven deployment means making ample use of unit checks to define and verify behavior.

Application Release Automation (ARA)

Tools, scripts or commodities that mechanically configure and efficiently configure a given model of a utility in a ready-to-use environment.

Canary Release

A go-live approach in which a new utility model is launched on a small subset of production servers and closely monitored to decide whether it behaves as expected. If found to be fully stable, the new model is brought into the full manufacturing environment.

Dark Launch

A go-live method in which code implementing new features is launched on a subset of the manufacturing environment but no longer visibly or partially enabled. However, the code is used in a manufacturing placement without the users being aware of it.

Regression Testing

End-to-end device testing to verify that current performance is no longer negatively impacted by application changes.