Top 100 Vocabulary for Adults | Cloud & DevOps Professionals
Cloud and DevOps vocabulary is the language of making software deployable, observable and recoverable. Professionals work across infrastructure, automation, deployment, security, monitoring and incident response so that change can move quickly without making the system fragile.
This profession-specific flagship belongs to the eduKate Adult Vocabulary for Professionals system. It complements Software & Technology Professionals, Cybersecurity Professionals and Data & Analytics Professionals.
The Four Banks
Cloud & Infrastructure: cloud, region, availability zone, instance, virtual machine, container, cluster, node, network, subnet, load balancer, storage, object storage, block storage, database, cache, DNS, CDN, IAM, secret, certificate, infrastructure as code, provisioning, autoscaling, serverless.
Delivery & Automation: repository, branch, commit, build, artifact, pipeline, CI, CD, deployment, release, environment, staging, production, rollback, blue-green, canary, feature flag, version, dependency, package, automation, configuration, orchestration, container image, registry.
Reliability & Observability: availability, reliability, scalability, elasticity, latency, throughput, saturation, error rate, SLI, SLO, SLA, monitoring, observability, metric, log, trace, dashboard, alert, threshold, incident, severity, root cause, postmortem, resilience, redundancy.
Operations & Security: on-call, runbook, playbook, escalation, maintenance, patching, backup, restore, disaster recovery, business continuity, failover, recovery time objective, recovery point objective, least privilege, encryption, firewall, vulnerability, secret management, audit, compliance, cost optimisation, tagging, ownership, drift, governance.
Top 100 Cloud & DevOps Vocabulary: Working Meanings
| # | Word | Professional meaning |
|---|---|---|
| 1 | Cloud | On-demand computing resources delivered through shared infrastructure and services. |
| 2 | Region | A geographic area containing cloud data-centre infrastructure. |
| 3 | Availability zone | An isolated location within a cloud region designed to improve resilience. |
| 4 | Instance | A provisioned unit of computing capacity. |
| 5 | Virtual machine | A software-defined computer running an operating system. |
| 6 | Container | A lightweight isolated package containing an application and its dependencies. |
| 7 | Cluster | A group of machines or nodes operating together. |
| 8 | Node | One machine participating in a cluster. |
| 9 | Network | A system connecting computing resources. |
| 10 | Subnet | A defined segment of an IP network. |
| 11 | Load balancer | A service distributing traffic across multiple resources. |
| 12 | Storage | Infrastructure used to persist data. |
| 13 | Object storage | Storage for data as individually addressable objects. |
| 14 | Block storage | Storage exposed as fixed-size blocks to computing systems. |
| 15 | Database | A system designed to store and retrieve structured data. |
| 16 | Cache | Fast temporary storage used to reduce repeated computation or retrieval. |
| 17 | DNS | Domain Name System, translating names into network addresses. |
| 18 | CDN | Content delivery network distributing content closer to users. |
| 19 | IAM | Identity and Access Management for controlling authentication and permissions. |
| 20 | Secret | Sensitive credential or key material used by systems. |
| 21 | Certificate | A digital credential binding identity to cryptographic keys. |
| 22 | Infrastructure as code | Defining infrastructure through version-controlled configuration. |
| 23 | Provisioning | Creating and configuring infrastructure resources. |
| 24 | Autoscaling | Automatic adjustment of computing capacity in response to demand. |
| 25 | Serverless | A cloud execution model where infrastructure management is largely abstracted from developers. |
| 26 | Repository | A version-controlled store of source code or configuration. |
| 27 | Branch | A separate line of development in version control. |
| 28 | Commit | A recorded set of version-controlled changes. |
| 29 | Build | The process of converting source into a deployable form. |
| 30 | Artifact | A generated package or output produced by a build. |
| 31 | Pipeline | An automated sequence of build, test and deployment steps. |
| 32 | CI | Continuous integration: frequent automated integration and testing of code changes. |
| 33 | CD | Continuous delivery or deployment: automated movement of changes toward production. |
| 34 | Deployment | Putting a software version into an environment. |
| 35 | Release | A version made available for use. |
| 36 | Environment | A defined infrastructure and configuration context. |
| 37 | Staging | A pre-production environment used for testing realistic deployments. |
| 38 | Production | The live environment serving real users. |
| 39 | Rollback | Reverting to a previous known-good version. |
| 40 | Blue-green | A deployment strategy switching traffic between two complete environments. |
| 41 | Canary | A deployment strategy exposing a small share of traffic before wider rollout. |
| 42 | Feature flag | A runtime switch controlling feature availability without redeployment. |
| 43 | Version | A distinct identified state of software or configuration. |
| 44 | Dependency | A library, service or resource on which software relies. |
| 45 | Package | A bundled software component distributed for installation or deployment. |
| 46 | Automation | Use of software to perform repeatable operational tasks. |
| 47 | Configuration | Settings controlling application or infrastructure behaviour. |
| 48 | Orchestration | Coordinated management of multiple services or containers. |
| 49 | Container image | A packaged template used to start containers. |
| 50 | Registry | A service storing and distributing software or container artifacts. |
| 51 | Availability | The proportion of time a service is usable. |
| 52 | Reliability | The ability to perform correctly and consistently over time. |
| 53 | Scalability | Ability to handle increased workload by adding resources. |
| 54 | Elasticity | Ability to adjust resources dynamically as demand changes. |
| 55 | Latency | The delay between request and response. |
| 56 | Throughput | The volume of work completed over time. |
| 57 | Saturation | The degree to which a resource is near its limit. |
| 58 | Error rate | The proportion of requests or operations that fail. |
| 59 | SLI | Service level indicator: a measured characteristic of service performance. |
| 60 | SLO | Service level objective: a target value for an SLI. |
| 61 | SLA | A service level agreement defining formal commitments. |
| 62 | Monitoring | Ongoing observation of system health and performance. |
| 63 | Observability | The ability to infer internal system state from metrics, logs and traces. |
| 64 | Metric | A quantitative measure of system behaviour. |
| 65 | Log | A recorded sequence of system events. |
| 66 | Trace | A record following a request across distributed components. |
| 67 | Dashboard | A visual display of operational measures. |
| 68 | Alert | A notification indicating a potentially important condition. |
| 69 | Threshold | A value triggering alert or action. |
| 70 | Incident | An event causing or risking unacceptable service impact. |
| 71 | Severity | The seriousness of an incident. |
| 72 | Root cause | A fundamental causal factor whose correction may reduce recurrence. |
| 73 | Postmortem | A structured review of an incident and lessons learned. |
| 74 | Resilience | Ability to withstand disruption and recover. |
| 75 | Redundancy | Additional capacity or components preserving service after failure. |
| 76 | On-call | A rotation assigning responsibility for urgent operational issues. |
| 77 | Runbook | A documented operational procedure. |
| 78 | Playbook | A structured response guide for a recurring scenario. |
| 79 | Escalation | Raising an issue to higher expertise or authority. |
| 80 | Maintenance | Work preserving system function. |
| 81 | Patching | Applying software updates to correct vulnerabilities or defects. |
| 82 | Backup | A recoverable copy of data or system state. |
| 83 | Restore | Returning data or systems from backup. |
| 84 | Disaster recovery | Restoration of systems after severe disruption. |
| 85 | Business continuity | Maintaining essential business functions through disruption. |
| 86 | Failover | Transfer to backup infrastructure after failure. |
| 87 | Recovery time objective | The target maximum time to restore a service after disruption. |
| 88 | Recovery point objective | The target maximum acceptable amount of data loss measured in time. |
| 89 | Least privilege | Granting only the minimum access required. |
| 90 | Encryption | Protecting information by transforming it using cryptography. |
| 91 | Firewall | A control filtering network traffic according to defined rules. |
| 92 | Vulnerability | A weakness that can be exploited or contribute to compromise. |
| 93 | Secret management | Controlled storage and distribution of sensitive credentials. |
| 94 | Audit | A structured review against defined requirements. |
| 95 | Compliance | Conformity with applicable rules and standards. |
| 96 | Cost optimisation | Reducing infrastructure cost while preserving required outcomes. |
| 97 | Tagging | Attaching metadata to resources for ownership, cost and management. |
| 98 | Ownership | Clear responsibility for a service or resource. |
| 99 | Drift | Unplanned difference between intended and actual configuration. |
| 100 | Governance | The structure of ownership, standards and accountability for cloud operations. |
Automation Makes Good Processes Faster—and Bad Ones Too
Automating a fragile deployment does not make it reliable. DevOps language keeps tests, rollback, observability and ownership attached to automation so speed does not merely accelerate failure.
Scenario: Deployment Causes Errors
Check error rate, latency, affected version, configuration, dependencies and whether the change can be rolled back safely. Restore service first; investigate deeper causality after impact is controlled.
Seven-Day Cloud & DevOps Vocabulary Plan
| Day | Practice |
|---|---|
| 1 | Map cloud regions, networks, compute and storage. |
| 2 | Trace one change through CI/CD to production. |
| 3 | Separate availability, reliability, scalability and elasticity. |
| 4 | Build a monitoring and observability map. |
| 5 | Practise incident, rollback and recovery language. |
| 6 | Recall 75+ cloud and DevOps terms. |
| 7 | Write a one-page service review balancing speed, reliability, security and cost. |
Continue the Digital Experience Wing
Conclusion
Cloud and DevOps vocabulary makes delivery infrastructure understandable. It helps professionals connect deployment speed to observability, operational ownership and recovery—so change remains reversible and systems remain dependable.