2663 terms covering AIOps, DevOps, MLOps, FinOps, observability and cloud-native operations.
Written by AI. Published under human oversight.
A/B Testing
A method of comparing two versions of a web page, app, or feature to determine which one performs better based on set metrics. A/B testing is commonly used in continuous delivery workflows to validate changes before full deployment.
Agile Development
An iterative approach to software development that facilitates rapid and flexible responses to change. Agile methods emphasize collaboration, customer feedback, and small, incremental releases.
Agile Methodology
Agile methodology is an iterative approach to software development that emphasizes collaboration, customer feedback, and rapid delivery. It promotes flexibility and responsiveness to changing requirements, aligning closely with DevOps principles.
API Management
API management encompasses the processes and tools that allow organizations to publish, document, and analyze their application programming interfaces (APIs). It ensures secure, scalable, and efficient access to backend services.
Artifact Repository
A centralized storage location for compiled binaries, container images, and other build artifacts. It ensures version control and traceability across deployments. Examples include Nexus and Artifactory.
Blue-Green Deployment
A release management strategy that reduces downtime and risk by ensuring that two identical environments are maintained. One environment serves live production traffic while the other is updated and tested before swapping traffic.
Blue-Green Deployments
Blue-Green deployment is a strategy that reduces downtime and risks by running two identical production environments called 'Blue' and 'Green.' One serves all traffic while the other is on standby, facilitating smooth transitions during releases.
Build Artifact Repository
A build artifact repository stores compiled binaries, container images, and deployment packages generated during software builds. It enables version tracking, dependency management, and reliable distribution across environments.
Build Automation
The use of software tools to automate the creation of executable applications from source code. This includes compiling code, running tests, and packaging applications, significantly speeding up the development process.
Canary Deployment
A deployment strategy that gradually rolls out changes to a small subset of users before a full-scale deployment. This approach allows teams to monitor performance and detect issues before affecting all users.
Canary Release
A deployment strategy where new features are gradually released to a small subset of users before full rollout. Performance and stability are monitored closely during this phase. This approach reduces the blast radius of potential failures.
Chaos Engineering
The practice of intentionally injecting failures into a system to test its resilience and improve its ability to handle unpredictable conditions. It promotes a culture of observability and encourages teams to proactively address weaknesses.
Cloud Infrastructure Management
The processes and practices involved in managing the hardware and software resources used to deliver cloud computing services. Effective cloud infrastructure management enhances resource optimization, security, and performance across distributed environments.
Collaboration Tools
Software applications that facilitate communication and collaboration among team members across various functions in an organization. Tools like Slack, Jira, and Confluence help to streamline workflows in a DevOps environment.
Configuration Drift
The gradual divergence of system configurations from their intended state due to manual changes or inconsistent updates. Drift can lead to instability and security vulnerabilities. IaC and configuration management tools help mitigate this risk.
Continuous Compliance
An automated approach to ensuring systems meet regulatory and policy requirements at all times. Compliance checks are embedded within CI/CD pipelines and infrastructure workflows. This reduces audit overhead and security risks.
Continuous Delivery
An extension of continuous integration that ensures code changes are automatically prepared for release to production at any time. It aims to minimize the friction of deploying code.
Continuous Delivery (CD)
An extension of Continuous Integration that automates the deployment process, allowing for code changes to be automatically released into production with minimal manual intervention. This ensures quick and reliable delivery of features to users.
Continuous Deployment
A DevOps practice in which validated code changes are automatically deployed to production without manual intervention. It relies heavily on automated testing and monitoring to minimize risk. This approach accelerates feedback and innovation cycles.
Continuous Integration (CI)
A development practice where code changes are automatically tested and merged into a shared repository frequently, usually multiple times a day. This helps to detect errors early, ensuring that the software is always in a deployable state.
Continuous Testing
An approach where automated tests are executed throughout the software delivery lifecycle. Continuous testing ensures rapid validation of code quality and business requirements.
Cross-Functional Teams
Teams composed of members from different functional areas such as development, operations, and quality assurance, promoting collaboration and accelerating project delivery.
Database Migration Automation
Automated processes and tools for managing schema changes, data migration, and version control for databases across environments. Ensures consistency and reduces manual errors in database deployments.
Dependency Management
The process of managing libraries and frameworks that a project relies on, ensuring compatibility and security throughout the development lifecycle. Effective dependency management can prevent vulnerabilities and assure application stability.
Deployment Freeze
A defined period during which code deployments are restricted, often due to high business risk events. It is used to maintain stability during critical operational windows.
Deployment Frequency
A key performance metric that measures how often code is deployed to production. High deployment frequency is associated with mature DevOps practices and rapid innovation cycles.
Deployment Orchestration
The automated coordination of multiple deployment tasks across environments and services. It manages dependencies, sequencing, and rollback procedures. Orchestration ensures consistent and reliable application releases.
DevOps Toolchain
An integrated set of tools that supports development, testing, deployment, and monitoring activities. Toolchains often combine CI/CD platforms, version control, and infrastructure automation solutions. Integration and interoperability are critical for efficiency.
DevSecOps
An approach that integrates security practices within the DevOps process, ensuring that security is a shared responsibility throughout the software development lifecycle. This allows for proactive identification and mitigation of vulnerabilities.
Digital Transformation
The integration of digital technology into all areas of a business, fundamentally changing how organizations operate and deliver value to customers. This often involves adopting DevOps practices to enhance agility and responsiveness.
Disaster Recovery Automation
Automated processes and tools for failing over to backup systems and recovering infrastructure and data after outages or disasters. Reduces RTO/RPO metrics and validates recovery procedures regularly.
Docker
An open-source platform used to automate the deployment of applications inside lightweight, portable containers. Docker simplifies the development and deployment of applications regardless of the environment.
Dynamic Application Security Testing (DAST)
A testing methodology that identifies security vulnerabilities in running applications through simulated attacks. DAST helps uncover runtime issues that static analysis tools may miss, ensuring a more secure application environment.
Environment Parity
The practice of keeping development, staging, and production environments as similar as possible. Environment parity reduces deployment issues caused by configuration inconsistencies.
Ephemeral Environment
A temporary, on-demand environment created for testing or feature validation and destroyed afterward. Ephemeral environments improve resource efficiency and accelerate development workflows.
Error Budget
A reliability metric representing the allowable level of service failure within a given period. It helps teams balance new feature development with system stability. Consuming the error budget too quickly can trigger release slowdowns.
Feature Flagging
A technique that enables teams to toggle features on or off at runtime without deploying new code. Feature flags support experimentation, gradual rollouts, and safer production testing.
Feature Flags
A technique that allows teams to enable or disable features in production without redeploying code. Feature flags support experimentation, A/B testing, and gradual rollouts. They decouple deployment from feature release.
Feature Toggle
A technique that enables developers to turn features on or off without deploying new code. Feature toggles facilitate continuous integration and delivery by decoupling feature releases from code changes.
Golden Image
A pre-configured virtual machine or container image used as a standardized baseline for deployments. Golden images ensure consistency and compliance across environments. They are commonly used in immutable infrastructure models.
Golden Image Pipeline
An automated process for building, validating, and distributing standardized machine or container images. Golden images ensure consistency and security across deployments.
Incident Response
A structured approach to addressing and managing the aftermath of a security breach or cyberattack. It includes detection, analysis, containment, eradication, and recovery phases.
Infrastructure as Code Testing
Automated validation and testing of infrastructure definitions before deployment, ensuring syntax correctness, security compliance, and alignment with organizational standards. Includes tools like Terraform validate and policy-as-code frameworks.
Infrastructure as Code Testing (IaC Testing)
Automated validation of infrastructure code for syntax errors, security vulnerabilities, and policy compliance before deployment. Prevents misconfigurations and security issues at infrastructure layer.
Infrastructure Automation
The application of software to create and manage infrastructure resources automatically, which minimizes manual intervention. This practice enhances speed, consistency, and reliability in provisioning and managing IT environments.
Infrastructure Automation Framework
Comprehensive platform or suite of tools that enables end-to-end automation of infrastructure provisioning, configuration, deployment, and management. Reduces manual toil and human error.
Infrastructure Cost Optimization
Strategies and tools for analyzing, monitoring, and reducing cloud and on-premises infrastructure spending. Includes resource right-sizing, usage analytics, and scheduling non-critical resources.
Infrastructure Drift
Unintended deviations between actual infrastructure state and desired/documented configuration state. Caused by manual changes, updates, or environmental factors, detected and corrected through compliance scanning.
Infrastructure Drift Remediation
The automated process of detecting and correcting deviations from desired infrastructure state definitions. It helps maintain consistency and compliance across environments.
Infrastructure Monitoring and Alerting
Continuous collection and analysis of metrics from infrastructure components to detect anomalies and trigger alerts on threshold breaches. Enables proactive identification of performance and availability issues.
Infrastructure Monitoring as Code
Approach to defining monitoring configurations, dashboards, and alerting rules in code form, enabling version control and automated deployment of observability infrastructure. Ensures monitoring consistency across environments.
Infrastructure Provisioning
The process of allocating and configuring compute, storage, and network resources for applications. Automation tools enable rapid and consistent environment creation. Provisioning is foundational to scalable DevOps practices.
Infrastructure Resilience Testing
Proactive testing of infrastructure and applications under failure conditions to validate recovery mechanisms and minimize downtime. Includes chaos engineering practices and disaster recovery drills.
Infrastructure Scaling Automation
Automated adjustment of computing resources based on demand metrics, allowing applications to scale up during peak usage and scale down during low periods. Improves efficiency and cost management.
Infrastructure Security Scanning
Automated analysis of infrastructure code, configurations, and deployed resources for security vulnerabilities, misconfigurations, and compliance violations. Identifies risks before they reach production.
Infrastructure Testing
Automated validation of infrastructure configurations, security policies, and compliance requirements before production deployment. Includes tools like Terraform testing, ServerSpec, and policy-as-code frameworks.
Infrastructure Versioning
Tracking and managing different versions of infrastructure configurations, similar to application code versioning. Enables reproducibility, rollback capabilities, and audit trails for infrastructure changes.
InnerSource
The practice of applying open-source collaboration principles within an organization. Teams share code, documentation, and best practices across internal repositories. InnerSource fosters transparency and innovation.
Kanban
A visual workflow management method used to define, manage, and improve services that deliver knowledge work. Kanban boards help teams visualize their work and limit work in progress to enhance flow.
Kubernetes Orchestration
The automated management of containerized applications using Kubernetes for deployment, scaling, and operations. It enables high availability, self-healing, and efficient resource utilization.
Lean Software Development
A methodology focused on maximizing value while minimizing waste throughout the software development process. Lean principles complement DevOps by promoting collaboration, efficiency, and continuous improvement.
Load Balancing
Load balancing is the process of distributing incoming network or application traffic across multiple servers to ensure no single server bears too much load. This improves application responsiveness and availability.
Load Balancing and Auto-scaling
Techniques for distributing traffic across multiple instances and automatically adjusting capacity based on demand metrics. Ensures high availability and optimizes resource utilization.
Load Balancing Strategy
Configuration of traffic distribution mechanisms across multiple application instances or servers to optimize performance and ensure high availability. Critical for scaling applications horizontally.
Logging and Monitoring
Critical practices in identifying the health and performance of applications and infrastructure. Effective logging and monitoring allow teams to detect anomalies, troubleshoot issues, and gain insights into usage patterns.
Mean Time to Recovery (MTTR)
A metric that measures the average time required to restore service after a failure. Lower MTTR indicates stronger incident response and resilient system design.
Metrics-Driven Development
An approach that leverages metrics and data to inform software development decisions and practices. Metrics-driven development enhances transparency and allows teams to make data-backed choices.
Microservices Architecture
An architectural style that structures an application as a collection of loosely coupled services, each responsible for a specific business functionality. This enhances modularity and allows independent development, deployment, and scaling.
Monitoring and Observability
Monitoring involves tracking system performance and availability, while observability refers to the ability to understand the internal state of a system based solely on its outputs. Together, they provide insights into application behavior and help identify issues.
Monitoring as Code
A practice that encompasses creating monitoring configurations and metrics definitions as software code that can be versioned and automated. This approach ensures more efficient monitoring practices and aligns monitoring with DevOps workflows.
Multi-Cloud DevOps Strategy
DevOps practices and tools designed to manage applications and infrastructure across multiple cloud providers simultaneously, avoiding vendor lock-in and optimizing cost and performance. Requires abstraction layers and multi-cloud orchestration.
Network as Code
Extension of Infrastructure as Code principles applied specifically to network configuration and management. Enables software-defined networking through programmable network definitions and automation.
Observability Stack
Integrated set of tools and practices for collecting metrics, logs, traces, and events to understand system behavior and troubleshoot issues. Forms the foundation for DevOps incident response.
Orchestration Platform
System that automates deployment, scaling, and management of containerized applications across clusters of machines. Examples include Kubernetes, Docker Swarm, and cloud-native platforms.
Peer Review
Peer review is a collaborative practice where developers review each other's code for quality, functionality, and adherence to standards before it is merged into the main codebase. This process improves code quality and knowledge sharing.
Platform Engineering
A discipline focused on building and maintaining internal developer platforms to streamline software delivery. It provides reusable tools, services, and workflows. Platform engineering enhances developer productivity and governance.
Progressive Delivery
A deployment approach that incrementally exposes new features to users while monitoring impact. It combines techniques like canary releases and feature flags. This method reduces deployment risk and improves user experience.
Pull Request
A method of submitting contributions to a project in version control systems, where changes are proposed, reviewed, and discussed before being merged into the main codebase. This encourages collaboration and code quality.
Regression Testing
A type of software testing that ensures that previously developed and tested software still performs after a change in code, preventing new features from inadvertently breaking existing functionality.
Release Management
The process of planning, scheduling, and controlling a software build through different stages of development and deployment. Effective release management ensures that software is released efficiently and reliably, minimizing risks and disruptions.
Release Orchestration
The coordination and automation of complex application releases across multiple teams and environments. It ensures consistent, compliant, and predictable deployments at scale.
Release Pipeline
A series of automated steps to build, test, and deploy software applications. Release pipelines facilitate continuous delivery by ensuring that applications are released consistently and reliably.
Resiliency Engineering
The practice of designing and building systems that can recover from failures gracefully and maintain their operational integrity. Resiliency engineering focuses on understanding failure modes and implementing practices to adopt fault tolerance.
Rolling Deployment
Gradual replacement strategy where old application instances are incrementally replaced with new versions while maintaining service availability. Balances deployment speed with zero-downtime requirements.
Secret Management
Secret management refers to securely storing, distributing, and rotating sensitive credentials such as API keys, passwords, and certificates. Effective secret management reduces exposure risks in automated delivery pipelines.
Serverless Architecture
A cloud-computing execution model where the cloud provider dynamically manages the allocation and provisioning of servers. Developers can focus on writing code without worrying about underlying infrastructure management, promoting agility and scalability.
Shadow IT
The use of IT resources without explicit approval from the IT department, which can lead to security risks and compliance issues. Managing and monitoring shadow IT is crucial for maintaining security in a DevOps environment.
Shift-Left Testing
A methodology that emphasizes early testing in the software development lifecycle. By identifying defects sooner, teams reduce remediation costs and improve product quality. Automated unit and integration testing are key enablers.
Silo Busting
The practice of breaking down silos within an organization to improve collaboration and communication between teams. It is vital for fostering a DevOps culture and enhancing productivity.
Site Reliability Engineering (SRE)
A discipline that incorporates aspects of software engineering and applies them to infrastructure and operations problems. SREs ensure that systems are reliable, scalable, and efficient, often using metrics and monitoring for continuous improvement.
Technical Debt
The implied cost of future refactoring or improvement caused by taking shortcuts in software development. Managing technical debt is crucial for maintaining software quality and sustainability in a fast-paced DevOps environment.
Trunk-Based Development
A source control strategy where developers frequently merge small changes into a shared main branch. It minimizes long-lived feature branches and reduces merge conflicts. This model supports rapid CI/CD workflows.
Value Stream Management
A practice that visualizes and optimizes the flow of work from idea to production. It identifies bottlenecks and inefficiencies in the software delivery pipeline. Metrics from VSM help improve speed and quality.
Value Stream Management (VSM)
Value Stream Management analyzes and optimizes the flow of work from idea to production. It provides visibility into bottlenecks, cycle times, and delivery efficiency. VSM helps DevOps teams align technical efforts with business outcomes.
Value Stream Mapping
A lean management method used to visualize and analyze the flow of work from idea to production. In DevOps, it identifies bottlenecks and inefficiencies in software delivery pipelines.
Version Control System (VCS)
A system that tracks changes to files and directories over time, allowing multiple developers to collaborate efficiently on projects. Git is a popular VCS that supports branching and merging, crucial for DevOps workflows.