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 "Incident Rollout Guard": Incident Rollout Guard is a devops release control that limits exposure during gradual deployment for response to service degradation. 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 Incident Rollout Guard when on-call received a high-severity page, so the team could reduce blast radius before the deployment window opened.”
机器辅助翻译草稿 (Chinese) for "Observability Artifact Signature": Observability Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for logs, metrics, traces, and events. 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 Observability Artifact Signature when latency increased after deploy, so the team could trust deployed packages before the deployment window opened.”
机器辅助翻译草稿 (Chinese) for "Release Trace Link": Release Trace Link is a devops observability link that connects a deployment or workflow to runtime evidence for versioned delivery of code or content. 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 Release Trace Link when the release notes were generated, so the team could debug production changes faster before the deployment window opened.”
机器辅助翻译草稿 (Chinese) for "Storage Isolation Boundary": Storage Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for persistent data and object access. 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 Storage Isolation Boundary when the workload read a large dataset, so the team could reduce cross-workload risk before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "Secret Approval Step": Secret Approval Step is a devops workflow control that requires review before a sensitive change proceeds for credential and sensitive configuration. 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 Secret Approval Step when a token rotated, so the team could keep high-risk automation accountable before the deployment window opened.”
机器辅助翻译草稿 (Chinese) for "Infrastructure Secret Rotation": Infrastructure Secret Rotation is a devops credential workflow that replaces sensitive keys without service interruption for cloud resources and platform wiring. 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 Infrastructure Secret Rotation when a new region was added, so the team could reduce credential exposure before the deployment window opened.”
机器辅助翻译草稿 (Chinese) for "Cluster Checkpoint Restore": Cluster Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for group of machines acting as one platform. It uses snapshots, state files, and integrity checks so teams can recover long-running work while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The platform engineering team used Cluster Checkpoint Restore when the cluster added a node pool, so the team could recover long-running work before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "Cluster Cold Start Budget": Cluster Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for group of machines acting as one platform. 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 Cluster Cold Start Budget when the cluster added a node pool, so the team could keep first requests responsive before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "GPU Placement Strategy": GPU Placement Strategy is a compute scheduling rule that chooses where workloads should run for accelerated compute for parallel workloads. 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 GPU Placement Strategy when the training job requested more memory, so the team could improve reliability and efficiency before the workload scaled up.”
机器辅助翻译草稿 (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.”