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
Automatischer Uebersetzungsentwurf (German) for "Storage Workload Priority": 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.
“Beispielentwurf: 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.”
Automatischer Uebersetzungsentwurf (German) for "Serverless Runtime Profile": 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.
“Beispielentwurf: 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.”
Automatischer Uebersetzungsentwurf (German) for "Infrastructure Approval Step": Infrastructure Approval Step is a devops workflow control that requires review before a sensitive change proceeds for cloud resources and platform wiring. It uses role checks, comments, and audit logs so teams can keep high-risk automation accountable while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The DevOps team used Infrastructure Approval Step when a new region was added, so the team could keep high-risk automation accountable before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Cache Image Hardening": Cache Image Hardening is a compute security practice that reduces risk inside packaged runtime images for fast temporary data layer. It uses minimal bases, patching, and vulnerability checks so teams can ship safer workloads while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Cache Image Hardening when the cache missed during peak traffic, so the team could ship safer workloads before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "GPU Image Hardening": GPU Image Hardening is a compute security practice that reduces risk inside packaged runtime images for accelerated compute for parallel workloads. It uses minimal bases, patching, and vulnerability checks so teams can ship safer workloads while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used GPU Image Hardening when the training job requested more memory, so the team could ship safer workloads before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Incident Approval Step": Incident Approval Step is a devops workflow control that requires review before a sensitive change proceeds for response to service degradation. It uses role checks, comments, and audit logs so teams can keep high-risk automation accountable while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The DevOps team used Incident Approval Step when on-call received a high-severity page, so the team could keep high-risk automation accountable before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Memory Isolation Boundary": Memory Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for volatile runtime storage. It uses namespaces, sandboxes, and access controls so teams can reduce cross-workload risk while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Memory Isolation Boundary when the process approached its memory limit, so the team could reduce cross-workload risk before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Runbook Secret Rotation": 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.
“Beispielentwurf: 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.”
Automatischer Uebersetzungsentwurf (German) for "Edge Cache Invalidation": Edge Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for globally distributed runtime. It uses keys, tags, timestamps, and purge events so teams can serve current results while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Edge Cache Invalidation when the request arrived near a user, so the team could serve current results before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Container Backpressure Control": Container Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for packaged application runtime. It uses queues, retry budgets, and admission control so teams can avoid overload cascades while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Container Backpressure Control when the image started on a new node, so the team could avoid overload cascades before the workload scaled up.”