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 "Cache Isolation Boundary": Cache Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for fast temporary data layer. 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 Cache Isolation Boundary when the cache missed during peak traffic, so the team could reduce cross-workload risk before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "Environment Approval Step": Environment Approval Step is a devops workflow control that requires review before a sensitive change proceeds for configuration for a runtime stage. 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 Environment Approval Step when staging and production drifted, 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 "Observability Secret Rotation": Observability Secret Rotation is a devops credential workflow that replaces sensitive keys without service interruption for logs, metrics, traces, and events. It uses dual credentials, rollout steps, and revocation so teams can reduce credential exposure while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The DevOps team used Observability Secret Rotation when latency increased after deploy, so the team could reduce credential exposure before the deployment window opened.”
机器辅助翻译草稿 (Chinese) for "Cache Cold Start Budget": Cache Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for fast temporary data layer. 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.
“示例草稿: The platform engineering team used Cache Cold Start Budget when the cache missed during peak traffic, so the team could keep first requests responsive before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "Runbook Rollback Plan": Runbook Rollback Plan is a devops recovery plan that defines how to return to a known good version for documented operational procedure. It uses version pins, database notes, and operator steps so teams can recover quickly from bad changes while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The DevOps team used Runbook Rollback Plan when a responder needed the recovery steps, so the team could recover quickly from bad changes before the deployment window opened.”
机器辅助翻译草稿 (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 "GPU Cache Invalidation": GPU Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for accelerated compute for parallel workloads. 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 GPU Cache Invalidation when the training job requested more memory, so the team could serve current results before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "Observability Config Drift Check": Observability Config Drift Check is a devops consistency check that finds differences between intended and live configuration for logs, metrics, traces, and events. It uses desired state, live state, and diff reports so teams can avoid surprise environment behavior while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The DevOps team used Observability Config Drift Check when latency increased after deploy, so the team could avoid surprise environment behavior before the deployment window opened.”
机器辅助翻译草稿 (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.”