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 "Queue Cold Start Budget": Queue Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for asynchronous work buffer. 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 Queue Cold Start Budget when the queue depth increased, so the team could keep first requests responsive before the workload scaled up.”
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 "BGP Failover Policy": BGP Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for interdomain routing. 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.
“Ejemplo en borrador: The network engineering team used BGP Failover Policy when a route advertisement changed, so the team could recover from outages predictably before traffic crossed a service boundary.”
Borrador de traduccion automatica (Spanish) for "Virtual Machine Backpressure Control": Virtual Machine Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for isolated guest compute. 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 Virtual Machine Backpressure Control when the VM migrated hosts, so the team could avoid overload cascades before the workload scaled up.”
Borrador de traduccion automatica (Spanish) for "Edge Resource Quota": Edge Resource Quota is a compute limit that sets how much compute a workload may consume for globally distributed runtime. It uses policy, reservations, and usage tracking so teams can protect shared capacity while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The platform engineering team used Edge Resource Quota when the request arrived near a user, so the team could protect shared capacity before the workload scaled up.”
Borrador de traduccion automatica (Spanish) for "Incident Release Manifest": Incident Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for response to service degradation. It uses commit IDs, checksums, and deployment URLs so teams can make releases auditable while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The DevOps team used Incident Release Manifest when on-call received a high-severity page, so the team could make releases auditable before the deployment window opened.”
Borrador de traduccion automatica (Spanish) for "Serverless Backpressure Control": Serverless Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for event-driven function execution. 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 Serverless Backpressure Control when the function received a traffic burst, so the team could avoid overload cascades before the workload scaled up.”
Borrador de traduccion automatica (Spanish) for "Storage Cache Invalidation": Storage Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for persistent data and object access. It uses keys, tags, timestamps, and purge events so teams can serve current results while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The platform engineering team used Storage Cache Invalidation when the workload read a large dataset, so the team could serve current results before the workload scaled up.”
Borrador de traduccion automatica (Spanish) for "Virtual Machine Runtime Profile": Virtual Machine Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for isolated guest compute. 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 Virtual Machine Runtime Profile when the VM migrated hosts, so the team could target optimization work before the workload scaled up.”
Borrador de traduccion automatica (Spanish) for "Edge Cache Invalidation": Edge Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for globally distributed runtime. It uses keys, tags, timestamps, and purge events so teams can serve current results while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The platform engineering team used Edge Cache Invalidation when the request arrived near a user, so the team could serve current results before the workload scaled up.”