Skip to content

Cloud & DevOps Terms

Essential terminology for cloud computing, containerization, CI/CD pipelines, and DevOps practices.

A methodology for software development emphasizing iterative development, collaboration, and flexibility to change.

The automatic adjustment of computational resources based on current demand, scaling up during high load and down during low load.

Isolated locations within a cloud region designed to be insulated from failures in other zones, providing high availability.

A deployment strategy that runs two identical production environments (blue and green), switching traffic between them to enable zero-downtime deployments.

A deployment strategy where a new version is gradually rolled out to a small subset of users before full deployment.

An automated process that builds, tests, and deploys code changes through stages from development to production.

The delivery of computing services (servers, storage, databases, networking, software) over the internet (“the cloud”).

The process of moving data, applications, and other business elements from on-premises infrastructure to cloud infrastructure.

Applications designed specifically to run in cloud environments, typically using containers, microservices, and dynamic orchestration.

A lightweight, standalone executable package that includes everything needed to run software: code, runtime, system tools, libraries, and settings.

The automated management, scaling, and networking of containers, typically using platforms like Kubernetes.

A software development practice where code changes are automatically deployed to production after passing automated tests.

A development practice where developers frequently integrate code into a shared repository, triggering automated builds and tests.

A set of practices combining software development (Dev) and IT operations (Ops) to shorten development lifecycle and deliver high-quality software.

A platform for developing, shipping, and running applications in containers, providing consistency across different environments.

A text file containing instructions for building a Docker image, specifying the base image, dependencies, and configuration.

A service that automatically distributes incoming application traffic across multiple targets for fault tolerance and high availability.

A specific instance of infrastructure and configuration where software runs (e.g., development, staging, production).

An operational framework using Git as the single source of truth for declarative infrastructure and application code.

A package manager for Kubernetes that helps define, install, and upgrade Kubernetes applications using charts.

A computing environment combining on-premises infrastructure, private cloud, and public cloud services.

The practice of managing and provisioning infrastructure through machine-readable definition files rather than manual configuration.

An approach where servers are never modified after deployment; updates require creating new servers and replacing old ones.

A virtual server in the cloud that runs applications and workloads.

An open-source container orchestration platform for automating deployment, scaling, and management of containerized applications.

The command-line tool for communicating with a Kubernetes cluster’s control plane.

The distribution of network traffic across multiple servers to ensure no single server bears too much demand.

An architectural approach where applications are built as a collection of small, independent services that communicate via APIs.

Using cloud services from multiple cloud providers to avoid vendor lock-in and leverage best-of-breed services.

The ability to measure the internal state of a system based on external outputs, typically using logs, metrics, and traces.

Infrastructure and software hosted on local servers rather than in the cloud.

An automated workflow that takes code from version control through build, test, and deployment stages.

The smallest deployable unit in Kubernetes, consisting of one or more containers that share storage and network resources.

Cloud infrastructure dedicated to a single organization, providing greater control and security.

Cloud services offered by third-party providers over the public internet, available to anyone who wants to use or purchase them.

A separate geographic area in cloud infrastructure, containing multiple availability zones for redundancy and low latency.

The process of reverting to a previous version of software when a deployment causes issues.

A deployment strategy where instances are gradually updated with new versions, maintaining availability throughout.

The ability to increase or decrease IT resources as needed to meet changing demand.

A cloud computing model where the cloud provider manages the infrastructure, allowing developers to focus on code without managing servers.

Infrastructure layer that manages service-to-service communication in microservices architectures, handling routing, load balancing, and security.

A discipline that applies software engineering principles to infrastructure and operations problems.

A pre-production environment that mirrors production, used for final testing before deployment.

An open-source Infrastructure as Code tool for building, changing, and versioning infrastructure safely and efficiently.

A software emulation of a physical computer that runs an operating system and applications.

An isolated virtual network within a cloud provider’s infrastructure where resources can be launched.

A human-readable data serialization language commonly used for configuration files in DevOps tools like Kubernetes and CI/CD pipelines.


These terms form the foundation of modern cloud and DevOps practices, essential for building and operating scalable applications.