DevOps Glossary
Modern engineering terminology, simplified for humans.
Blue-Green Deployment
A release management strategy that utilizes two identical production environments (Blue and Green) to reduce downtime and risk by running only one at a time.
Canary Deployment
A pattern for rolling out new versions of software by first deploying to a small subset of users before rolling it out to the entire infrastructure.
Chaos Engineering
The discipline of experimenting on a software system in production in order to build confidence in the system's capability to withstand turbulent and unexpected conditions.
Circuit Breaker
A design pattern used in software development to detect failures and encapsulate the logic of preventing a failure from constantly recurring during maintenance, temporary external system failure or unexpected system difficulties.
Drift Detection
The process of identifying differences between the actual state of infrastructure and its desired state as defined in code (IaC).
GitOps
An operational framework that takes DevOps best practices used for application development, such as version control, collaboration, compliance, and CI/CD, and applies them to infrastructure automation.
Idempotency
The property of certain operations in mathematics and computer science whereby they can be applied multiple times without changing the result beyond the initial application.
Infrastructure as Code (IaC)
The process of managing and provisioning computer data centers through machine-readable definition files, rather than physical hardware configuration or interactive configuration tools.
Observability
The ability to measure the internal state of a system by examining its outputs (logs, metrics, and traces).
Service Level Objective (SLO)
A target value or range of values for a service level that is measured by a Service Level Indicator (SLI).
Missing a term?
Our glossary is community-driven. If there's a term you'd like to see added, let us know and we'll break it down.
Suggest a Term