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
Borrador de traduccion automatica (Spanish) for "Memory Autoscaling Policy": Memory Autoscaling Policy is a compute control loop that changes capacity based on demand signals for volatile runtime storage. It uses metrics, thresholds, and cooldowns so teams can match resources to load while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The platform engineering team used Memory Autoscaling Policy when the process approached its memory limit, so the team could match resources to load before the workload scaled up.”
Borrador de traduccion automatica (Spanish) 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.
“Ejemplo en borrador: 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.”
Borrador de traduccion automatica (Spanish) for "Scheduler Autoscaling Policy": Scheduler Autoscaling Policy is a compute control loop that changes capacity based on demand signals for placement of work onto resources. It uses metrics, thresholds, and cooldowns so teams can match resources to load while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The platform engineering team used Scheduler Autoscaling Policy when the cluster needed to place a job, so the team could match resources to load before the workload scaled up.”
Borrador de traduccion automatica (Spanish) 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.
“Ejemplo en borrador: 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.”
Borrador de traduccion automatica (Spanish) for "CPU Checkpoint Restore": CPU Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for general-purpose processor scheduling. 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.
“Ejemplo en borrador: The platform engineering team used CPU Checkpoint Restore when the service hit a compute ceiling, so the team could recover long-running work before the workload scaled up.”
Borrador de traduccion automatica (Spanish) for "DNS Resolver Cache": DNS Resolver Cache is a networking performance layer that stores DNS answers for reuse until they expire for name resolution and delegation. It uses TTL rules, cache keys, and invalidation so teams can reduce lookup latency while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The network engineering team used DNS Resolver Cache when a resolver returned stale data, so the team could reduce lookup latency before traffic crossed a service boundary.”
Borrador de traduccion automatica (Spanish) 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.
“Ejemplo en borrador: 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.”
Borrador de traduccion automatica (Spanish) for "Serverless Isolation Boundary": Serverless Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for event-driven function execution. It uses namespaces, sandboxes, and access controls so teams can reduce cross-workload risk while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The platform engineering team used Serverless Isolation Boundary when the function received a traffic burst, so the team could reduce cross-workload risk before the workload scaled up.”
Borrador de traduccion automatica (Spanish) for "Scheduler Runtime Profile": Scheduler Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for placement of work onto resources. It uses sampling, traces, and resource metrics so teams can target optimization work while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The platform engineering team used Scheduler Runtime Profile when the cluster needed to place a job, so the team could target optimization work before the workload scaled up.”
Borrador de traduccion automatica (Spanish) for "Virtual Machine Cold Start Budget": Virtual Machine Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for isolated guest compute. 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.
“Ejemplo en borrador: The platform engineering team used Virtual Machine Cold Start Budget when the VM migrated hosts, so the team could keep first requests responsive before the workload scaled up.”