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 "DNS Path Trace": DNS Path Trace is a networking diagnostic record that shows where traffic travels and where delay or loss appears for name resolution and delegation. It uses hop data, timing, and network metadata so teams can debug connectivity issues while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The network engineering team used DNS Path Trace when a resolver returned stale data, so the team could debug connectivity issues before traffic crossed a service boundary.”
Automatischer Uebersetzungsentwurf (German) for "Serverless Capacity Forecast": Serverless Capacity Forecast is a compute planning model that estimates future resource needs for event-driven function execution. It uses traffic history, growth assumptions, and utilization trends so teams can avoid surprise shortages while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Serverless Capacity Forecast when the function received a traffic burst, so the team could avoid surprise shortages before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Cache Workload Priority": Cache Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for fast temporary data layer. 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 Cache Workload Priority when the cache missed during peak traffic, so the team could protect critical paths before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "TLS Traffic Shaper": TLS Traffic Shaper is a networking control mechanism that limits or prioritizes flows across links for encrypted transport setup. 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.
“Beispielentwurf: The network engineering team used TLS Traffic Shaper when a certificate neared expiration, so the team could protect important traffic before traffic crossed a service boundary.”
Automatischer Uebersetzungsentwurf (German) for "Virtual Machine Runtime Profile": Virtual Machine Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for isolated guest compute. 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 Virtual Machine Runtime Profile when the VM migrated hosts, so the team could target optimization work before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "DNS Failover Policy": 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.
“Beispielentwurf: 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.”
Automatischer Uebersetzungsentwurf (German) for "Cache Runtime Profile": 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.
“Beispielentwurf: 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.”
Automatischer Uebersetzungsentwurf (German) for "Memory Placement Strategy": Memory Placement Strategy is a compute scheduling rule that chooses where workloads should run for volatile runtime storage. 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.
“Beispielentwurf: The platform engineering team used Memory Placement Strategy when the process approached its memory limit, so the team could improve reliability and efficiency before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Scheduler Image Hardening": Scheduler Image Hardening is a compute security practice that reduces risk inside packaged runtime images for placement of work onto resources. 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 Scheduler Image Hardening when the cluster needed to place a job, so the team could ship safer workloads before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Scheduler Cold Start Budget": Scheduler Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for placement of work onto resources. 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.
“Beispielentwurf: The platform engineering team used Scheduler Cold Start Budget when the cluster needed to place a job, so the team could keep first requests responsive before the workload scaled up.”