Professional Documents
Culture Documents
DevOps glossary
TABLE O F C O NT ENTS
Azure
Microsoft’s pay-per-use cloud service with worldwide data centers. The service includes:
Blue/Green deployments
A popular deployment pattern. A Blue/Green pattern uses 2 production environments that swap
roles between live and staging with each release.
For example, if the live version of an application is on your blue server, you use the green server
for staging and testing before redirecting traffic to it. After cutover, the blue server then acts as
the new staging area.
Build servers save developers time otherwise spent on manual processes, while process
repetition makes results more predictable.
Canary deployments
A popular deployment pattern. A canary pattern releases updates to a handful of production
targets for testing before rolling out to the rest.
Named after the old early warning system for miners, it helps detect problems early and without
impacting your whole service.
Chaos Engineering
Chaos engineering is a method that allows for failures while still providing an acceptable
service for users.
Popularized by Netflix (who built a tool called Chaos Monkey that randomly causes production
failures), chaos engineering accepts problems happen and encourages building system
reliance.
CI/CD
CI/CD describes the combined practices of Continuous Integration and Continuous Delivery.
Together they form DevOps’ most important workflows.
Code promotion
The process of successfully tested code moving through your development environments. For
example, code deployed to a test environment may get promoted to a production environment if
it passes QA testing.
Container registry
A container registry catalogs and stores container images. It acts as a directory for team
members and deployment processes.
Container
A lightweight virtual machine that runs or hosts an application. Usually hosted on cloud
services.
Containers are non-changeable and disposable. Developers usually launch new versions of their
products on new containers and destroy the old ones.
Container image
A container image is the definition or template of what will become a running application in a
container.
Much like Continuous Integration, Continuous Delivery involves automating as many of its
processes as possible. It can also include human steps, such as testing and approvals.
Continuous Integration also involves automating processes between code commits and
creation of a deployable artifact.
That includes:
Compiling of code
Automatic testing
Packaging of successful code
Read An introduction to build servers and continuous integration for more information.
Deployment
A deployment is the process of sending or installing deployable artifacts to targets where
applications will run.
That could include physical and virtual media like servers or cloud solutions.
Deployment pattern
A deployment pattern is a strategy that helps reduce downtime and other problems when
deploying applications.
There are many standard deployment patterns, like Rolling, Blue/Green, and Canary.
Read Common deployment patterns and how to set them up in Octopus for more information.
Deployment target
A deployment target is a physical or virtualized server or cloud service where you deploy your
application for testing or use.
DevOps
DevOps is a development methodology that helps tear down barriers in software delivery,
including:
Manual processes
Office politics
Counterintuitive support workflows
Docker
Docker provides the leading technology for building and running containers. The Docker format,
OCI, is open source and industry standard, supported by all major operating systems.
Docker Hub
Docker Hub is Docker’s container registry service. It allows developers to catalog and store
container images.
DORA metrics
DORA is the DevOps Research and Assessment group.
DORA metrics are a predictive link between DevOps practices and business outcomes. You can
use Dora metrics to measure the progress of DevOps adoption.
Dynamic infrastructure
Dynamic infrastructure describes resources you can spin up and tear down on demand.
Dynamic infrastructure can include containers or virtual machines.
Environments
An environment is a collection of deployment targets. It could include physical or virtual
servers, and cloud services.
Environments also form a deployment’s lifecycle. Most development teams use at least 3
environments like:
Development
Test
Production
A deployment gets promoted through these environments as it passes checks and testing.
Feature branching
Feature branching is the Git practice of working in distributed development.
This means developers work on new features in separate branches and merge changes into the
main branch when complete.
Git
Git is a software and method of source control used for distributed development. Git tracks file
changes, mostly to track source code changes between developers.
GitHub Actions
GitHub Actions is GitHub feature that allows you to perform build functions from your code
repository without a build server.
Read How GitHub Actions is different to traditional build servers for more information.
GitHub
GitHub is a code repository hosting service for Git-controlled source code.
GitHub is one of the most popular code hosting services. It’s popular with both the open-source
community and corporate organizations.
GitOps
GitOps is a framework to automate infrastructure processes using DevOps tools and concepts.
With version control you can manage infrastructure and environment definitions with existing
tooling.
Helm
Helm is a Kubernetes package manager. Helm uses “Helm Charts” to define and install
applications on a Kubernetes cluster.
I
Software tools can use the files to spin up, configure, and tear down infrastructure.
The IDP should reduce complexity and cognitive overload for developers.
Jenkins Pipeline
Jenkins Pipeline is a group of plugins Jenkins recommends for setting up a Continuous Delivery
platform.
Jenkins
Jenkins is an open-source build server, Continuous Integration (CI), and automation platform.
Jenkins will compile and test your code, trigger packaging, and hand off to your deployment
tool.
K
Kubernetes
Kubernetes is a container management tool that can help you scale an application.
Kubernetes can spin up and tear down automatically as your processes or traffic needs
change.
L
N/A
Microservices
Microservices is a software architecture method where you build an application from many
independent services. Users access the software through a single front end, unaware of the
difference.
The benefit of microservices is if one service has a problem, the application can still run
without it. It’s also quicker to recover from problems.
Read Monoliths vs. Microservices and Microservices and Frameworks for more information.
N
N/A
O
N/A
Platform engineering
Platform Engineering is a DevOps team structure that balances autonomy with standard
processes. It treats ideal tech and an automated deployment pipeline as one product offered to
internal development teams.
Easy self-service
Ensures following of established practices
Less risk caused by decision making
Q
N/A
Release management
Release management is the process of promoting software versions through environments
with version control.
Rolling deployments
A popular deployment pattern. A rolling pattern deploys to one target (or batch of targets) at a
time. This method helps reduce downtime and environment congestion during rollout.
Runbooks
Runbooks are a step-by-step guide to complete a routine or emergency computer process.
Shadow IT
Shadow IT is when people outside of IT use or install tools that their IT department should
oversee.
Shadow IT reduces resource transparency and control and adds risk to organizations.
As with Platform Engineering, SRE helps development teams build scalable and reliable
applications. Developers use tools provided by SREs, reducing manual work and introducing
capabilities like observability.
T
Tenants
Tenants is an Octopus feature deploying to Software as a Service (SaaS) applications. They
allow you to deliver your package to groups of environments or projects.
Terraform
Developed by Hashicorp, Terraform is a cloud infrastructure management tool. Terraform uses
Infrastructure as Code to automate infrastructure setup and operations.
U
N/A
Version control
Version control is a tool used to track changes to code and other files. It can also store build
processes and infrastructure config.
W
N/A
X
N/A
Y
N/A
Z
N/A
Send feedback
Categories: DevOps
NEXT ARTICLE
Share
Search
More resources
Measuring Platform
Developer
Engineering with
experience metrics
MONK metrics
Read more Read more
CATEGORIES TAGS
DevOps Improvement
History Metrics
QUICK LINKS
Octopus Deploy
Back to top