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
Infrastructure Config Drift Check is a devops consistency check that finds differences between intended and live configuration for cloud resources and platform wiring. It uses desired state, live state, and diff reports so teams can avoid surprise environment behavior while keeping evidence, reliability, and public-safe operational boundaries clear.
“The DevOps team used Infrastructure Config Drift Check when a new region was added, so the team could avoid surprise environment behavior before the deployment window opened.”
Edge Image Hardening is a compute security practice that reduces risk inside packaged runtime images for globally distributed runtime. It uses minimal bases, patching, and vulnerability checks so teams can ship safer workloads while keeping evidence, reliability, and public-safe operational boundaries clear.
“The platform engineering team used Edge Image Hardening when the request arrived near a user, so the team could ship safer workloads before the workload scaled up.”
GPU Placement Strategy is a compute scheduling rule that chooses where workloads should run for accelerated compute for parallel workloads. It uses affinity, topology, availability, and cost signals so teams can improve reliability and efficiency while keeping evidence, reliability, and public-safe operational boundaries clear.
“The platform engineering team used GPU Placement Strategy when the training job requested more memory, so the team could improve reliability and efficiency before the workload scaled up.”
DNS Resolver Cache is a networking performance layer that stores DNS answers for reuse until they expire for name resolution and delegation. It uses TTL rules, cache keys, and invalidation so teams can reduce lookup latency while keeping evidence, reliability, and public-safe operational boundaries clear.
“The network engineering team used DNS Resolver Cache when a resolver returned stale data, so the team could reduce lookup latency before traffic crossed a service boundary.”
CPU Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for general-purpose processor scheduling. 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 CPU Isolation Boundary when the service hit a compute ceiling, so the team could reduce cross-workload risk before the workload scaled up.”
BGP Rate Limit is a networking traffic control that caps request volume over a period for interdomain routing. It uses identity keys, windows, and response policies so teams can protect services from overload while keeping evidence, reliability, and public-safe operational boundaries clear.
“The network engineering team used BGP Rate Limit when a route advertisement changed, so the team could protect services from overload before traffic crossed a service boundary.”
Release Incident Timeline is a devops response record that orders alerts, actions, and decisions during an incident for versioned delivery of code or content. It uses timestamps, owners, and evidence links so teams can learn from outages without guesswork while keeping evidence, reliability, and public-safe operational boundaries clear.
“The DevOps team used Release Incident Timeline when the release notes were generated, so the team could learn from outages without guesswork before the deployment window opened.”
Serverless Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for event-driven function execution. 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 Serverless Runtime Profile when the function received a traffic burst, so the team could target optimization work before the workload scaled up.”
Observability Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for logs, metrics, traces, and events. It uses cryptographic signatures, provenance, and verification so teams can trust deployed packages while keeping evidence, reliability, and public-safe operational boundaries clear.
“The DevOps team used Observability Artifact Signature when latency increased after deploy, so the team could trust deployed packages before the deployment window opened.”
DNS Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for name resolution and delegation. It uses health signals, priorities, and cooldown windows so teams can recover from outages predictably while keeping evidence, reliability, and public-safe operational boundaries clear.
“The network engineering team used DNS Failover Policy when a resolver returned stale data, so the team could recover from outages predictably before traffic crossed a service boundary.”