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
机器辅助翻译草稿 (Chinese) 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.
“示例草稿: 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.”
机器辅助翻译草稿 (Chinese) for "GPU Runtime Profile": GPU Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for accelerated compute for parallel workloads. 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 GPU Runtime Profile when the training job requested more memory, so the team could target optimization work before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "Observability Approval Step": Observability Approval Step is a devops workflow control that requires review before a sensitive change proceeds for logs, metrics, traces, and events. 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.
“示例草稿: The DevOps team used Observability Approval Step when latency increased after deploy, so the team could keep high-risk automation accountable before the deployment window opened.”
机器辅助翻译草稿 (Chinese) for "TLS Resolver Cache": TLS Resolver Cache is a networking performance layer that stores DNS answers for reuse until they expire for encrypted transport setup. 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 TLS Resolver Cache when a certificate neared expiration, so the team could reduce lookup latency before traffic crossed a service boundary.”
机器辅助翻译草稿 (Chinese) for "Queue Backpressure Control": Queue Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for asynchronous work buffer. 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 Queue Backpressure Control when the queue depth increased, so the team could avoid overload cascades before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "Edge Autoscaling Policy": Edge Autoscaling Policy is a compute control loop that changes capacity based on demand signals for globally distributed runtime. 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 Edge Autoscaling Policy when the request arrived near a user, so the team could match resources to load before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "Queue Cache Invalidation": Queue Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for asynchronous work buffer. It uses keys, tags, timestamps, and purge events so teams can serve current results while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The platform engineering team used Queue Cache Invalidation when the queue depth increased, so the team could serve current results before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "Release Rollout Guard": Release Rollout Guard is a devops release control that limits exposure during gradual deployment for versioned delivery of code or content. 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 Release Rollout Guard when the release notes were generated, so the team could reduce blast radius before the deployment window opened.”
机器辅助翻译草稿 (Chinese) for "Cache Capacity Forecast": Cache Capacity Forecast is a compute planning model that estimates future resource needs for fast temporary data layer. 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.
“示例草稿: The platform engineering team used Cache Capacity Forecast when the cache missed during peak traffic, so the team could avoid surprise shortages before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "Incident Trace Link": Incident Trace Link is a devops observability link that connects a deployment or workflow to runtime evidence for response to service degradation. 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 Incident Trace Link when on-call received a high-severity page, so the team could debug production changes faster before the deployment window opened.”