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 Anycast Endpoint": TLS Anycast Endpoint is a networking routing pattern that advertises one address from multiple locations for encrypted transport setup. It uses regional announcements, health checks, and traffic steering so teams can serve users from nearby healthy sites while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The network engineering team used TLS Anycast Endpoint when a certificate neared expiration, so the team could serve users from nearby healthy sites before traffic crossed a service boundary.”
机器辅助翻译草稿 (Chinese) for "Runbook Artifact Signature": Runbook Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for documented operational procedure. 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 Runbook Artifact Signature when a responder needed the recovery steps, so the team could trust deployed packages before the deployment window opened.”
机器辅助翻译草稿 (Chinese) 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.
“示例草稿: 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.”
机器辅助翻译草稿 (Chinese) for "Serverless Isolation Boundary": Serverless Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for event-driven function execution. 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 Serverless Isolation Boundary when the function received a traffic burst, so the team could reduce cross-workload risk before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "Storage Autoscaling Policy": Storage Autoscaling Policy is a compute control loop that changes capacity based on demand signals for persistent data and object access. 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 Storage Autoscaling Policy when the workload read a large dataset, so the team could match resources to load before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "Scheduler Workload Priority": Scheduler Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for placement of work onto resources. 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 Scheduler Workload Priority when the cluster needed to place a job, so the team could protect critical paths before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "Serverless Placement Strategy": Serverless Placement Strategy is a compute scheduling rule that chooses where workloads should run for event-driven function execution. 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.
“示例草稿: The platform engineering team used Serverless Placement Strategy when the function received a traffic burst, so the team could improve reliability and efficiency before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "GPU Workload Priority": GPU Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for accelerated compute for parallel workloads. 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 GPU Workload Priority when the training job requested more memory, so the team could protect critical paths before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "Infrastructure Runbook Check": Infrastructure Runbook Check is a devops operational test that confirms that documented procedures still work for cloud resources and platform wiring. 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 Infrastructure Runbook Check when a new region was added, so the team could keep response playbooks current before the deployment window opened.”
机器辅助翻译草稿 (Chinese) for "BGP Resolver Cache": BGP Resolver Cache is a networking performance layer that stores DNS answers for reuse until they expire for interdomain routing. 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 BGP Resolver Cache when a route advertisement changed, so the team could reduce lookup latency before traffic crossed a service boundary.”