Define the new internet.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
2,337 definitions
Runbook Secret Rotation is a devops credential workflow that replaces sensitive keys without service interruption for documented operational procedure. It uses dual credentials, rollout steps, and revocation so teams can reduce credential exposure while keeping evidence, reliability, and public-safe operational boundaries clear.
“The DevOps team used Runbook Secret Rotation when a responder needed the recovery steps, so the team could reduce credential exposure before the deployment window opened.”
Release Trace Link is a devops observability link that connects a deployment or workflow to runtime evidence for versioned delivery of code or content. It uses trace IDs, span metadata, and release identifiers so teams can debug production changes faster while keeping evidence, reliability, and public-safe operational boundaries clear.
“The DevOps team used Release Trace Link when the release notes were generated, so the team could debug production changes faster before the deployment window opened.”
Incident Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for response to service degradation. It uses commit IDs, checksums, and deployment URLs so teams can make releases auditable while keeping evidence, reliability, and public-safe operational boundaries clear.
“The DevOps team used Incident Release Manifest when on-call received a high-severity page, so the team could make releases auditable before the deployment window opened.”
Observability Rollout Guard is a devops release control that limits exposure during gradual deployment for logs, metrics, traces, and events. It uses traffic slices, health checks, and automatic pause rules so teams can reduce blast radius while keeping evidence, reliability, and public-safe operational boundaries clear.
“The DevOps team used Observability Rollout Guard when latency increased after deploy, so the team could reduce blast radius before the deployment window opened.”
Serverless Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for event-driven function execution. It uses namespaces, sandboxes, and access controls so teams can reduce cross-workload risk while keeping evidence, reliability, and public-safe operational boundaries clear.
“The platform engineering team used Serverless Isolation Boundary when the function received a traffic burst, so the team could reduce cross-workload risk before the workload scaled up.”
Release Infra Plan is a devops change preview that shows expected infrastructure changes before apply for versioned delivery of code or content. It uses resource graphs, policy checks, and cost notes so teams can review platform changes safely while keeping evidence, reliability, and public-safe operational boundaries clear.
“The DevOps team used Release Infra Plan when the release notes were generated, so the team could review platform changes safely before the deployment window opened.”
Cache Autoscaling Policy is a compute control loop that changes capacity based on demand signals for fast temporary data layer. It uses metrics, thresholds, and cooldowns so teams can match resources to load while keeping evidence, reliability, and public-safe operational boundaries clear.
“The platform engineering team used Cache Autoscaling Policy when the cache missed during peak traffic, so the team could match resources to load before the workload scaled up.”
Cluster Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for group of machines acting as one platform. It uses prewarming, smaller packages, and runtime tuning so teams can keep first requests responsive while keeping evidence, reliability, and public-safe operational boundaries clear.
“The platform engineering team used Cluster Cold Start Budget when the cluster added a node pool, so the team could keep first requests responsive before the workload scaled up.”
Cache Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for fast temporary data layer. It uses sampling, traces, and resource metrics so teams can target optimization work while keeping evidence, reliability, and public-safe operational boundaries clear.
“The platform engineering team used Cache Runtime Profile when the cache missed during peak traffic, so the team could target optimization work before the workload scaled up.”
Storage Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for persistent data and object access. It uses priority classes, preemption rules, and fairness limits so teams can protect critical paths while keeping evidence, reliability, and public-safe operational boundaries clear.
“The platform engineering team used Storage Workload Priority when the workload read a large dataset, so the team could protect critical paths before the workload scaled up.”