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 "Serverless Resource Quota": Serverless Resource Quota is a compute limit that sets how much compute a workload may consume for event-driven function execution. 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 Serverless Resource Quota when the function received a traffic burst, so the team could protect shared capacity before the workload scaled up.”
Borrador de traduccion automatica (Spanish) for "Serverless Cold Start Budget": Serverless Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for event-driven function execution. 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 Serverless Cold Start Budget when the function received a traffic burst, so the team could keep first requests responsive before the workload scaled up.”
Borrador de traduccion automatica (Spanish) for "Serverless Image Hardening": Serverless Image Hardening is a compute security practice that reduces risk inside packaged runtime images for event-driven function execution. 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 Serverless Image Hardening when the function received a traffic burst, so the team could ship safer workloads before the workload scaled up.”
Borrador de traduccion automatica (Spanish) for "Runbook Rollback Plan": Runbook Rollback Plan is a devops recovery plan that defines how to return to a known good version for documented operational procedure. 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.
“Ejemplo en borrador: The DevOps team used Runbook Rollback Plan when a responder needed the recovery steps, so the team could recover quickly from bad changes before the deployment window opened.”
Borrador de traduccion automatica (Spanish) for "Container Autoscaling Policy": Container Autoscaling Policy is a compute control loop that changes capacity based on demand signals for packaged application runtime. 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 Container Autoscaling Policy when the image started on a new node, so the team could match resources to load before the workload scaled up.”
Borrador de traduccion automatica (Spanish) for "BGP Path Trace": BGP Path Trace is a networking diagnostic record that shows where traffic travels and where delay or loss appears for interdomain routing. It uses hop data, timing, and network metadata so teams can debug connectivity issues while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The network engineering team used BGP Path Trace when a route advertisement changed, so the team could debug connectivity issues before traffic crossed a service boundary.”
Borrador de traduccion automatica (Spanish) for "Runbook Artifact Signature": Runbook Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for documented operational procedure. It uses cryptographic signatures, provenance, and verification so teams can trust deployed packages while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The DevOps team used Runbook Artifact Signature when a responder needed the recovery steps, so the team could trust deployed packages before the deployment window opened.”
Borrador de traduccion automatica (Spanish) for "Release Trace Link": Release Trace Link is a devops observability link that connects a deployment or workflow to runtime evidence for versioned delivery of code or content. It uses trace IDs, span metadata, and release identifiers so teams can debug production changes faster while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The DevOps team used Release Trace Link when the release notes were generated, so the team could debug production changes faster before the deployment window opened.”
Borrador de traduccion automatica (Spanish) for "Storage Workload Priority": Storage Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for persistent data and object access. 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.
“Ejemplo en borrador: The platform engineering team used Storage Workload Priority when the workload read a large dataset, so the team could protect critical paths before the workload scaled up.”
Borrador de traduccion automatica (Spanish) for "Secret Build Gate": Secret Build Gate is a devops quality gate that blocks promotion when required checks fail for credential and sensitive configuration. It uses tests, lint, security scans, and policy rules so teams can prevent broken releases while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The DevOps team used Secret Build Gate when a token rotated, so the team could prevent broken releases before the deployment window opened.”