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 "Release Incident Timeline": Release Incident Timeline is a devops response record that orders alerts, actions, and decisions during an incident for versioned delivery of code or content. It uses timestamps, owners, and evidence links so teams can learn from outages without guesswork while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The DevOps team used Release Incident Timeline when the release notes were generated, so the team could learn from outages without guesswork before the deployment window opened.”
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 "BGP Certificate Monitor": BGP Certificate Monitor is a networking security monitor that tracks certificate validity and configuration for interdomain routing. 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 BGP Certificate Monitor when a route advertisement changed, so the team could avoid trust failures before traffic crossed a service boundary.”
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 "TLS Traffic Shaper": TLS Traffic Shaper is a networking control mechanism that limits or prioritizes flows across links for encrypted transport setup. It uses queues, rate limits, and quality-of-service rules so teams can protect important traffic while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The network engineering team used TLS Traffic Shaper when a certificate neared expiration, so the team could protect important traffic before traffic crossed a service boundary.”
Borrador de traduccion automatica (Spanish) for "Serverless Workload Priority": Serverless Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for event-driven function execution. 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 Serverless Workload Priority when the function received a traffic burst, so the team could protect critical paths 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 "DNS Rate Limit": DNS Rate Limit is a networking traffic control that caps request volume over a period for name resolution and delegation. It uses identity keys, windows, and response policies so teams can protect services from overload while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The network engineering team used DNS Rate Limit when a resolver returned stale data, so the team could protect services from overload 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 "Container Runtime Profile": Container Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for packaged application runtime. 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 Container Runtime Profile when the image started on a new node, so the team could target optimization work before the workload scaled up.”