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
DNS Traffic Shaper is a networking control mechanism that limits or prioritizes flows across links for name resolution and delegation. It uses queues, rate limits, and quality-of-service rules so teams can protect important traffic while keeping evidence, reliability, and public-safe operational boundaries clear.
“The network engineering team used DNS Traffic Shaper when a resolver returned stale data, so the team could protect important traffic before traffic crossed a service boundary.”
Scheduler Autoscaling Policy is a compute control loop that changes capacity based on demand signals for placement of work onto resources. 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 Scheduler Autoscaling Policy when the cluster needed to place a job, so the team could match resources to load before the workload scaled up.”
Serverless Image Hardening is a compute security practice that reduces risk inside packaged runtime images for event-driven function execution. 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 Serverless Image Hardening when the function received a traffic burst, so the team could ship safer workloads before the workload scaled up.”
CPU Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for general-purpose processor scheduling. 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 CPU Workload Priority when the service hit a compute ceiling, so the team could protect critical paths before the workload scaled up.”
Serverless Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for event-driven function execution. 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 Serverless Workload Priority when the function received a traffic burst, so the team could protect critical paths before the workload scaled up.”
Storage Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for persistent data and object access. It uses queues, retry budgets, and admission control so teams can avoid overload cascades while keeping evidence, reliability, and public-safe operational boundaries clear.
“The platform engineering team used Storage Backpressure Control when the workload read a large dataset, so the team could avoid overload cascades before the workload scaled up.”
Infrastructure Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for cloud resources and platform wiring. 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 Infrastructure Release Manifest when a new region was added, so the team could make releases auditable before the deployment window opened.”
Storage Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for persistent data and object access. 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 Storage Isolation Boundary when the workload read a large dataset, so the team could reduce cross-workload risk before the workload scaled up.”
Incident Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for response to service degradation. 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 Incident Artifact Signature when on-call received a high-severity page, so the team could trust deployed packages before the deployment window opened.”
Runbook Infra Plan is a devops change preview that shows expected infrastructure changes before apply for documented operational procedure. 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 Runbook Infra Plan when a responder needed the recovery steps, so the team could review platform changes safely before the deployment window opened.”