Comprehensive DevOps Glossary, Tool Periodic Table, and Skill Roadmap

This article, originally sourced from the DevOpsGeek publication, compiles a comprehensive glossary of DevOps terminology, an illustrated periodic table of DevOps tools, and a visual skill roadmap for practitioners.

A/B Testing – Using A/B testing to release different variants of a feature to separate user groups and evaluate them through metrics and behavior.

Acceptance Testing – High‑level testing of the entire system to determine whether new and existing functionality meet production quality standards.

Agent – A program installed on a specific physical server that handles the execution of various processes on that server.

Agile – The predecessor of DevOps; an iterative software development (and broader business) methodology that emphasizes short planning cycles, predictability, and adaptability to changing requirements.

ARA (Application Release Automation) – Tools, scripts, or products that automatically install and correctly configure a given application version in the target environment.

Behavior‑Driven Development (BDD) – A development approach that specifies software behavior in a business‑readable syntax.

Black Box Testing – A QA practice that validates external behavior without knowledge of the system’s internal workings.

Build Agent – A CI build agent, installed locally or remotely, that communicates with the CI server to send and receive build‑related messages.

Build Artifact Repository – A repository that organizes build artifacts with metadata and enables automated publishing and consumption.

Build Automation – Tools or frameworks that automatically compile source code into publishable binaries, often including unit tests.

Canary Release – An incremental rollout strategy that deploys a new version to a small subset of production servers and monitors its behavior before full rollout.

Configuration Drift – Inconsistencies between actual system configurations and the template version caused by manual hot‑fixes that are not captured in the template.

Configuration Management – Practices and tools for establishing and maintaining consistent system settings, often used for IT infrastructure automation.

Continuous Delivery (CD) – A set of processes and practices that eliminate waste in software production, enabling faster, higher‑quality releases and rapid feedback loops.

Continuous Integration (CI) – A development practice where developers frequently merge code into a shared repository, triggering automated builds and early defect detection.

Dark Launch – A rollout strategy where new code is deployed to a subset of production but remains invisible or partially activated to users.

Delivery Pipeline – An orchestrated, automated sequence of tasks that implements the software delivery process for a new application version.

DevOps – A cultural and professional movement that promotes collaboration between development and IT operations to improve communication, workflow, and software delivery speed.

DevOps Intelligence – Insight‑driven capabilities that enable more efficient, lower‑risk, and higher‑quality software delivery.

Functional Testing – End‑to‑end testing of (new) functionality using executable specifications.

Infrastructure as a Service (IaaS) – Cloud‑hosted virtual machines billed on a pay‑as‑you‑go basis, giving users full control over the OS and middleware.

Infrastructure as Code (IaC) – A configuration‑management technique where infrastructure definitions are stored as code and applied automatically.

Lean – A methodology that reduces waste by focusing on value‑adding steps; originally from manufacturing and now applied to software development.

Microservice – An architectural style where a complex application is composed of small, independently deployable services communicating via language‑agnostic APIs.

Non‑functional Requirements (NFRs) – Quality attributes such as usability, latency, scalability, and performance that describe how a feature should behave.

NoOps – An approach where system management is fully outsourced to a PaaS provider or fully automated, minimizing internal operations effort.

Orchestration Pipeline – Tools or products that invoke and coordinate the various automated tasks that form a continuous delivery pipeline.

Platform as a Service (PaaS) – Cloud‑hosted runtime environments where users supply application code and limited configuration, while the provider manages middleware and databases.

Product Owner – The role responsible for defining, prioritizing, and maintaining the backlog of unfinished features and work, commonly found in Agile teams.

Provisioning – The process of preparing a new system (often virtualized) for developers or testers, typically automated via configuration‑management tools.

Regression Testing – End‑to‑end testing to ensure that recent changes have not adversely affected existing functionality.

Release Coordination – Defining and executing all actions required to move code from commit to production, often fully automated in a CD environment.

Release Management – Managing the end‑to‑end process of delivering software from development through to production release.

Release Orchestration – Using tools such as XL Release to manage and visualize the software release workflow.

Test‑Driven Development (TDD) – A development practice where tests are written before code; tests initially fail, then code is added to make them pass.

Unit Testing – Code‑level tests that verify the behavior of individual code units without requiring a full end‑to‑end system.

Value Stream Mapping – A visualization technique used in Lean to identify value‑adding steps and eliminate waste in a process.

Virtualization – A system‑management method that runs applications on simulated machines rather than physical hardware, enabling rapid creation, cloning, and disposal of virtual machines.

Waterfall – A stage‑gated software development methodology that progresses sequentially from requirements gathering to development and release.

White Box Testing – QA practice that validates internal system behavior by inspecting the system during execution.

Reference: https://xebialabs.com/glossary

DevOps Tool Periodic Table – An industry‑recognized collection of 120 DevOps tools (version 3.0) organized into categories such as Analytics and AIOps, available for free and interactive.

The table allows users to select a tool and instantly generate a visual DevOps pipeline diagram via XebiaLabs’ integrated Diagram Generator, which can be customized, downloaded, printed, and shared.

Because DevOps tools evolve rapidly, the periodic table provides a clear, interactive overview of the current market, indicating whether each tool is open‑source or commercial.

About XebiaLabs: The company develops enterprise‑grade continuous delivery and DevOps software that gives organizations visibility, automation, and control for faster, lower‑risk software delivery.

For more details, visit https://xebialabs.com/periodic-table-of-devops-tools/.

DevOps Skill Map – A visual roadmap that outlines the knowledge areas and technologies a practitioner should master, including programming languages (Python, Ruby, Node.js, Go, Rust, C/C++), OS concepts, Linux administration, terminal proficiency, networking and security fundamentals, load balancers and web servers, containerization (Docker, rkt, LXC), cloud platforms (AWS, Azure, GCP, etc.), infrastructure‑as‑code tools (Terraform, CloudFormation, Ansible, etc.), CI/CD systems (Jenkins, Travis, CircleCI, etc.), monitoring and alerting solutions, log management (ELK), container orchestration (Kubernetes, Mesos, Docker Swarm, Nomad), and post‑incident analysis habits.

Images for the tool table and skill map are sourced from XebiaLabs and GitHub repositories (e.g., https://github.com/lucassha/DevOps-Student-Roadmap and https://github.com/kamranahmedse/developer-roadmap).