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 "DNS Failover Policy": DNS Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for name resolution and delegation. It uses health signals, priorities, and cooldown windows so teams can recover from outages predictably while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The network engineering team used DNS Failover Policy when a resolver returned stale data, so the team could recover from outages predictably before traffic crossed a service boundary.”
Rascunho de traducao automatica (Portuguese) for "Infrastructure Artifact Signature": Infrastructure Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for cloud resources and platform wiring. 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 Infrastructure Artifact Signature when a new region was added, so the team could trust deployed packages before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "GPU Image Hardening": GPU Image Hardening is a compute security practice that reduces risk inside packaged runtime images for accelerated compute for parallel workloads. It uses minimal bases, patching, and vulnerability checks so teams can ship safer workloads while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The platform engineering team used GPU Image Hardening when the training job requested more memory, so the team could ship safer workloads before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Scheduler Checkpoint Restore": Scheduler Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for placement of work onto resources. 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 Scheduler Checkpoint Restore when the cluster needed to place a job, so the team could recover long-running 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 "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.
“Exemplo em rascunho: The DevOps team used Observability Secret Rotation when latency increased after deploy, so the team could reduce credential exposure before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "GPU Checkpoint Restore": GPU Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for accelerated compute for parallel workloads. 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 GPU Checkpoint Restore when the training job requested more memory, so the team could recover long-running work before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "GPU Cold Start Budget": GPU Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for accelerated compute for parallel workloads. 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.
“Exemplo em rascunho: The platform engineering team used GPU Cold Start Budget when the training job requested more memory, so the team could keep first requests responsive before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Scheduler Isolation Boundary": Scheduler Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for placement of work onto resources. 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 Scheduler Isolation Boundary when the cluster needed to place a job, so the team could reduce cross-workload risk before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Storage Backpressure Control": Storage Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for persistent data and object access. 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 Storage Backpressure Control when the workload read a large dataset, so the team could avoid overload cascades before the workload scaled up.”