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 "Edge Backpressure Control": Edge Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for globally distributed runtime. 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 Edge Backpressure Control when the request arrived near a user, so the team could avoid overload cascades 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 "Release Incident Timeline": Release Incident Timeline is a devops response record that orders alerts, actions, and decisions during an incident for versioned delivery of code or content. 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 Release Incident Timeline when the release notes were generated, so the team could learn from outages without guesswork before the deployment window opened.”
机器辅助翻译草稿 (Chinese) for "Infrastructure Incident Timeline": Infrastructure Incident Timeline is a devops response record that orders alerts, actions, and decisions during an incident for cloud resources and platform wiring. 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 Infrastructure Incident Timeline when a new region was added, so the team could learn from outages without guesswork before the deployment window opened.”
机器辅助翻译草稿 (Chinese) for "Container Autoscaling Policy": Container Autoscaling Policy is a compute control loop that changes capacity based on demand signals for packaged application 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 Container Autoscaling Policy when the image started on a new node, so the team could match resources to load before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "Incident Artifact Signature": Incident Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for response to service degradation. 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 Incident Artifact Signature when on-call received a high-severity page, so the team could trust deployed packages before the deployment window opened.”
机器辅助翻译草稿 (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 "DNS Rate Limit": DNS Rate Limit is a networking traffic control that caps request volume over a period for name resolution and delegation. It uses identity keys, windows, and response policies so teams can protect services from overload while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The network engineering team used DNS Rate Limit when a resolver returned stale data, so the team could protect services from overload before traffic crossed a service boundary.”
机器辅助翻译草稿 (Chinese) for "Queue Capacity Forecast": Queue Capacity Forecast is a compute planning model that estimates future resource needs for asynchronous work buffer. 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 Queue Capacity Forecast when the queue depth increased, so the team could avoid surprise shortages before the workload scaled up.”