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 "Edge Isolation Boundary": Edge Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for globally distributed runtime. 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 Edge Isolation Boundary when the request arrived near a user, so the team could reduce cross-workload risk before the workload scaled up.”
Borrador de traduccion automatica (Spanish) for "Queue Placement Strategy": Queue Placement Strategy is a compute scheduling rule that chooses where workloads should run for asynchronous work buffer. It uses affinity, topology, availability, and cost signals so teams can improve reliability and efficiency while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The platform engineering team used Queue Placement Strategy when the queue depth increased, so the team could improve reliability and efficiency before the workload scaled up.”
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 "TLS Anycast Endpoint": TLS Anycast Endpoint is a networking routing pattern that advertises one address from multiple locations for encrypted transport setup. It uses regional announcements, health checks, and traffic steering so teams can serve users from nearby healthy sites while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The network engineering team used TLS Anycast Endpoint when a certificate neared expiration, so the team could serve users from nearby healthy sites before traffic crossed a service boundary.”
Borrador de traduccion automatica (Spanish) for "Queue Backpressure Control": Queue Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for asynchronous work buffer. 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 Queue Backpressure Control when the queue depth increased, so the team could avoid overload cascades before the workload scaled up.”
Borrador de traduccion automatica (Spanish) for "GPU Cache Invalidation": GPU Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for accelerated compute for parallel workloads. 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 GPU Cache Invalidation when the training job requested more memory, so the team could serve current results 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 "GPU Workload Priority": GPU Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for accelerated compute for parallel workloads. 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 GPU Workload Priority when the training job requested more memory, so the team could protect critical paths before the workload scaled up.”
Borrador de traduccion automatica (Spanish) for "Storage Autoscaling Policy": Storage Autoscaling Policy is a compute control loop that changes capacity based on demand signals for persistent data and object access. 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 Storage Autoscaling Policy when the workload read a large dataset, so the team could match resources to load before the workload scaled up.”
Borrador de traduccion automatica (Spanish) for "Incident Artifact Signature": Incident Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for response to service degradation. 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 Incident Artifact Signature when on-call received a high-severity page, so the team could trust deployed packages before the deployment window opened.”