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 "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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) 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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) for "Queue Backpressure Control": Queue Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for asynchronous work buffer. 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 Queue Backpressure Control when the queue depth increased, so the team could avoid overload cascades before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Secret Rollback Plan": Secret Rollback Plan is a devops recovery plan that defines how to return to a known good version for credential and sensitive configuration. 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.
“Exemplo em rascunho: The DevOps team used Secret Rollback Plan when a token rotated, so the team could recover quickly from bad changes before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "GPU Runtime Profile": GPU Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for accelerated compute for parallel workloads. It uses sampling, traces, and resource metrics so teams can target optimization work while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The platform engineering team used GPU Runtime Profile when the training job requested more memory, so the team could target optimization work before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) 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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) for "DNS Anycast Endpoint": DNS Anycast Endpoint is a networking routing pattern that advertises one address from multiple locations for name resolution and delegation. 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.
“Exemplo em rascunho: The network engineering team used DNS Anycast Endpoint when a resolver returned stale data, so the team could serve users from nearby healthy sites before traffic crossed a service boundary.”
Rascunho de traducao automatica (Portuguese) 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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) for "Container Checkpoint Restore": Container Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for packaged application runtime. 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.
“Exemplo em rascunho: The platform engineering team used Container Checkpoint Restore when the image started on a new node, so the team could recover long-running work before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Cache Workload Priority": Cache Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for fast temporary data layer. 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 Cache Workload Priority when the cache missed during peak traffic, so the team could protect critical paths before the workload scaled up.”