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 "Storage Isolation Boundary": Storage Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for persistent data and object access. 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 Storage Isolation Boundary when the workload read a large dataset, so the team could reduce cross-workload risk before the workload scaled up.”
Borrador de traduccion automatica (Spanish) for "Scheduler Cold Start Budget": Scheduler Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for placement of work onto resources. 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 Scheduler Cold Start Budget when the cluster needed to place a job, so the team could keep first requests responsive 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 "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 "Infrastructure Rollout Guard": Infrastructure Rollout Guard is a devops release control that limits exposure during gradual deployment for cloud resources and platform wiring. It uses traffic slices, health checks, and automatic pause rules so teams can reduce blast radius while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The DevOps team used Infrastructure Rollout Guard when a new region was added, so the team could reduce blast radius before the deployment window opened.”
Borrador de traduccion automatica (Spanish) for "Infrastructure Rollback Plan": Infrastructure Rollback Plan is a devops recovery plan that defines how to return to a known good version for cloud resources and platform wiring. 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 Infrastructure Rollback Plan when a new region was added, 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 "Memory Resource Quota": Memory Resource Quota is a compute limit that sets how much compute a workload may consume for volatile runtime storage. 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 Memory Resource Quota when the process approached its memory limit, so the team could protect shared capacity before the workload scaled up.”
Borrador de traduccion automatica (Spanish) for "Incident Infra Plan": Incident Infra Plan is a devops change preview that shows expected infrastructure changes before apply for response to service degradation. It uses resource graphs, policy checks, and cost notes so teams can review platform changes safely while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The DevOps team used Incident Infra Plan when on-call received a high-severity page, so the team could review platform changes safely before the deployment window opened.”
Borrador de traduccion automatica (Spanish) for "Incident Approval Step": Incident Approval Step is a devops workflow control that requires review before a sensitive change proceeds for response to service degradation. 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.
“Ejemplo en borrador: The DevOps team used Incident Approval Step when on-call received a high-severity page, so the team could keep high-risk automation accountable before the deployment window opened.”