- A/B Testing
- Agile
- Automation
- Blue/Green Deployment
- Build
- Canary Release
- Chaos Engineering
- CI/CD
- Cloud-Native
- Code Review
- Configuration Management
- Container
- Continuous Testing
- DevOps Culture
- Docker
- Environment
- Feedback Loop
- Idempotence
- Immutable Infrastructure
- Infrastructure as Code (IaC)
- Infrastructure Monitoring
- Jenkins
- Kubernetes
- Microservices
- Monitoring
- Pipeline
- Post-Mortem Analysis
- Provisioning
- Release
- Repository (Repo)
- Rollback
- Scalability
- Shift Left
- Smoke Testing
- Source Code Management (SCM)
- Vagrant
- Version Control
- Virtual Machine
A/B Testing
A/B Testing is a randomized experiment involving two versions of a webpage, feature, or product to determine which performs better with respect to specific metrics or objectives.
View the Term »Agile
Agile is a software development methodology that emphasizes flexibility, collaboration, and customer-centricity.
View the Term »Automation
Automation refers to using technology to perform tasks without human intervention, leveraging software, hardware, and algorithms to replicate and optimize manual processes.
View the Term »Blue/Green Deployment
Blue/Green Deployment is a release strategy where two separate environments, blue for the current version and green for the new version, are used to manage releases.
View the Term »Build
The build process is the transformation of source code into executable artifacts, including compiling, linking, and packaging code into a format suitable for deployment.
View the Term »Canary Release
A Canary Release is a release strategy where new software versions are gradually deployed to a subset of users or environments, allowing for controlled testing, validation, and adaptation.
View the Term »Chaos Engineering
Chaos Engineering involves intentionally introducing problems, like failures, delays, or errors, into systems to determine weaknesses, vulnerabilities, and limitations.
View the Term »CI/CD
Continuous Integration and Continuous Deployment/Delivery (CI/CD) is a DevOps practice that automates the integration, testing, and deployment of code changes.
View the Term »Cloud-Native
Cloud-Native refers to the practice of building, deploying, and running applications that take full advantage of cloud computing benefits.
View the Term »Code Review
Code review involves the systematic examination of software source code to identify defects, vulnerabilities, or improvements.
View the Term »Configuration Management
Configuration Management deals with systematically handling changes in a system to maintain its integrity, consistency, and reliability.
View the Term »Container
Containers are stand-alone, lightweight software packages that include everything needed to run a piece of software, such as code, runtime, libraries, and system tools.
View the Term »Continuous Testing
Continuous Testing involves executing automated tests at different stages of the software development lifecycle.
View the Term »DevOps Culture
DevOps culture refers to a cultural shift emphasizing collaboration, communication, and integration between development and operations teams.
View the Term »Docker
Docker is an open-source platform for developing, shipping, and running containers.
View the Term »Environment
An environment refers to the combination of hardware and software where an application or system runs.
View the Term »Feedback Loop
A feedback loop is a process where information from previous actions informs subsequent actions, creating a cycle of continuous learning and improvement.
View the Term »Idempotence
Idempotence refers to operations or functions that produce the same result regardless of how many times they are applied.
View the Term »Immutable Infrastructure
Immutable Infrastructure is an approach where infrastructure entities, like VMs, containers, and configurations, are never modified after deployment.
View the Term »Infrastructure as Code (IaC)
Infrastructure as Code (IaC) is the practice of managing and provisioning infrastructure using code or script, applying software development principles like version control, automation, and collaboration to infrastructure management.
View the Term »Infrastructure Monitoring
Infrastructure Monitoring involves the continuous tracking of IT infrastructure components such as servers, networks, storage, and databases.
View the Term »Jenkins
Jenkins is an open-source automation server widely used for implementing Continuous Integration and Continuous Deployment (CI/CD) workflows.
View the Term »Kubernetes
Kubernetes is an open-source platform designed for deploying, scaling, and managing containerized applications.
View the Term »Microservices
Microservices architecture refers to a design approach where applications are composed of small, independent services running as separate processes, each performing a specific function and communicating via well-defined APIs.
View the Term »Monitoring
Monitoring is the continuous observation of a system's performance, functionality, and health, tracking metrics, logs, and events to ensure stability, efficiency, and quality.
View the Term »Pipeline
A pipeline represents automated processes for transforming software from source code to production-ready artifacts.
View the Term »Post-Mortem Analysis
Post-mortem analysis is the investigation and root cause analysis conducted after an incident or failure.
View the Term »Provisioning
Provisioning refers to the process of setting up IT infrastructure, including hardware, software, networks, and configurations.
View the Term »Release
A release refers to the process of launching a new version or update of software, making it available to end-users.
View the Term »Repository (Repo)
A repository, or repo, is a centralized location where code is stored and managed.
View the Term »Rollback
Rollback refers to reverting to a previous stable version of software or configuration after a failed update, patch, or release.
View the Term »Scalability
Scalability refers to a system's ability to grow and handle increased demand without significant degradation in performance or functionality.
View the Term »Shift Left
Shift Left is a strategy that involves ensuring code quality earlier in the development process.
View the Term »Smoke Testing
Smoke Testing involves preliminary testing of software to identify high-level and critical issues before detailed testing or release.
View the Term »Source Code Management (SCM)
Source Code Management (SCM) encompasses tools and practices for tracking and controlling changes to source code.
View the Term »Vagrant
Vagrant is an open-source tool for building, maintaining, and managing virtualized development environments.
View the Term »Version Control
Version control systems record changes to files over time, allowing specific versions to be recalled, compared, and merged.
View the Term »Virtual Machine
A virtual machine is an emulation of a computer system, running on physical hardware through a virtualization layer.
View the Term »