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 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 "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 "CPU Workload Priority": CPU Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for general-purpose processor scheduling. 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 CPU Workload Priority when the service hit a compute ceiling, so the team could protect critical paths before the workload scaled up.”
Borrador de traduccion automatica (Spanish) for "Secret Secret Rotation": Secret Secret Rotation is a devops credential workflow that replaces sensitive keys without service interruption for credential and sensitive configuration. It uses dual credentials, rollout steps, and revocation so teams can reduce credential exposure while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The DevOps team used Secret Secret Rotation when a token rotated, so the team could reduce credential exposure before the deployment window opened.”
Borrador de traduccion automatica (Spanish) for "Serverless Isolation Boundary": Serverless Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for event-driven function execution. 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 Serverless Isolation Boundary when the function received a traffic burst, so the team could reduce cross-workload risk before the workload scaled up.”
Borrador de traduccion automatica (Spanish) for "Memory Runtime Profile": Memory Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for volatile runtime storage. 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 Memory Runtime Profile when the process approached its memory limit, 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.”
Borrador de traduccion automatica (Spanish) for "Cache Runtime Profile": Cache Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for fast temporary data layer. 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 Cache Runtime Profile when the cache missed during peak traffic, so the team could target optimization work before the workload scaled up.”
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 "Container Checkpoint Restore": Container Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for packaged application runtime. It uses snapshots, state files, and integrity checks so teams can recover long-running work while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The platform engineering team used Container Checkpoint Restore when the image started on a new node, so the team could recover long-running work before the workload scaled up.”