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 "TLS Egress Policy": TLS Egress Policy is a networking outbound control that decides where workloads may send traffic for encrypted transport setup. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The network engineering team used TLS Egress Policy when a certificate neared expiration, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”
机器辅助翻译草稿 (Chinese) for "Edge Runtime Profile": Edge Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for globally distributed runtime. 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 Edge Runtime Profile when the request arrived near a user, so the team could target optimization work before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "Incident Release Manifest": Incident Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for response to service degradation. 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 Incident Release Manifest when on-call received a high-severity page, so the team could make releases auditable before the deployment window opened.”
机器辅助翻译草稿 (Chinese) for "Cache Backpressure Control": Cache Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for fast temporary data layer. 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 Cache Backpressure Control when the cache missed during peak traffic, so the team could avoid overload cascades before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "Container Isolation Boundary": Container Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for packaged application runtime. 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 Container Isolation Boundary when the image started on a new node, so the team could reduce cross-workload risk before the workload scaled up.”
机器辅助翻译草稿 (Chinese) 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.
“示例草稿: 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.”
机器辅助翻译草稿 (Chinese) for "DNS Ingress Rule": DNS Ingress Rule is a networking boundary rule that controls how external traffic enters a service for name resolution and delegation. It uses hostnames, paths, protocols, and policy checks so teams can keep entry points predictable while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The network engineering team used DNS Ingress Rule when a resolver returned stale data, so the team could keep entry points predictable before traffic crossed a service boundary.”
机器辅助翻译草稿 (Chinese) for "Incident Runbook Check": Incident Runbook Check is a devops operational test that confirms that documented procedures still work for response to service degradation. It uses dry runs, screenshots, and command validation so teams can keep response playbooks current while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The DevOps team used Incident Runbook Check when on-call received a high-severity page, so the team could keep response playbooks current before the deployment window opened.”
机器辅助翻译草稿 (Chinese) for "Scheduler Autoscaling Policy": 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.”
机器辅助翻译草稿 (Chinese) for "Runbook Incident Timeline": Runbook Incident Timeline is a devops response record that orders alerts, actions, and decisions during an incident for documented operational procedure. 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 Runbook Incident Timeline when a responder needed the recovery steps, so the team could learn from outages without guesswork before the deployment window opened.”