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
Rascunho de traducao automatica (Portuguese) for "Cluster Workload Priority": Cluster Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for group of machines acting as one platform. 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.
“Exemplo em rascunho: The platform engineering team used Cluster Workload Priority when the cluster added a node pool, so the team could protect critical paths before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "BGP Certificate Monitor": BGP Certificate Monitor is a networking security monitor that tracks certificate validity and configuration for interdomain routing. It uses expiry checks, chain validation, and alerting so teams can avoid trust failures while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The network engineering team used BGP Certificate Monitor when a route advertisement changed, so the team could avoid trust failures before traffic crossed a service boundary.”
Rascunho de traducao automatica (Portuguese) 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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) for "Observability Trace Link": Observability Trace Link is a devops observability link that connects a deployment or workflow to runtime evidence for logs, metrics, traces, and events. 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.
“Exemplo em rascunho: The DevOps team used Observability Trace Link when latency increased after deploy, so the team could debug production changes faster before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Runbook Runbook Check": Runbook Runbook Check is a devops operational test that confirms that documented procedures still work for documented operational procedure. 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.
“Exemplo em rascunho: The DevOps team used Runbook Runbook Check when a responder needed the recovery steps, so the team could keep response playbooks current before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) 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.
“Exemplo em rascunho: The DevOps team used Observability Artifact Signature when latency increased after deploy, so the team could trust deployed packages before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Release Runbook Check": Release Runbook Check is a devops operational test that confirms that documented procedures still work for versioned delivery of code or content. 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.
“Exemplo em rascunho: The DevOps team used Release Runbook Check when the release notes were generated, so the team could keep response playbooks current before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) 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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) 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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) for "Incident Secret Rotation": Incident Secret Rotation is a devops credential workflow that replaces sensitive keys without service interruption for response to service degradation. It uses dual credentials, rollout steps, and revocation so teams can reduce credential exposure while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The DevOps team used Incident Secret Rotation when on-call received a high-severity page, so the team could reduce credential exposure before the deployment window opened.”