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 Certificate Monitor": DNS Certificate Monitor is a networking security monitor that tracks certificate validity and configuration for name resolution and delegation. 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 DNS Certificate Monitor when a resolver returned stale data, so the team could avoid trust failures before traffic crossed a service boundary.”
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 "Storage Autoscaling Policy": Storage Autoscaling Policy is a compute control loop that changes capacity based on demand signals for persistent data and object access. It uses metrics, thresholds, and cooldowns so teams can match resources to load while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The platform engineering team used Storage Autoscaling Policy when the workload read a large dataset, so the team could match resources to load before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Serverless Autoscaling Policy": Serverless Autoscaling Policy is a compute control loop that changes capacity based on demand signals for event-driven function execution. It uses metrics, thresholds, and cooldowns so teams can match resources to load while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The platform engineering team used Serverless Autoscaling Policy when the function received a traffic burst, so the team could match resources to load before the workload scaled up.”
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 "Scheduler Placement Strategy": Scheduler Placement Strategy is a compute scheduling rule that chooses where workloads should run for placement of work onto resources. 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 Scheduler Placement Strategy when the cluster needed to place a job, so the team could improve reliability and efficiency before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Release Config Drift Check": Release Config Drift Check is a devops consistency check that finds differences between intended and live configuration for versioned delivery of code or content. 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 Release Config Drift Check when the release notes were generated, so the team could avoid surprise environment behavior before the deployment window opened.”
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.”
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 "DNS Health Probe": DNS Health Probe is a networking availability check that tests whether a service or path can receive traffic for name resolution and delegation. It uses timed requests, thresholds, and regional checks so teams can send traffic only to healthy targets while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The network engineering team used DNS Health Probe when a resolver returned stale data, so the team could send traffic only to healthy targets before traffic crossed a service boundary.”