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
Brouillon de traduction automatique (French) 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.
“Exemple en brouillon: 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.”
Brouillon de traduction automatique (French) for "CPU Checkpoint Restore": CPU Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for general-purpose processor scheduling. 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.
“Exemple en brouillon: The platform engineering team used CPU Checkpoint Restore when the service hit a compute ceiling, so the team could recover long-running work before the workload scaled up.”
Brouillon de traduction automatique (French) for "Storage Resource Quota": Storage Resource Quota is a compute limit that sets how much compute a workload may consume for persistent data and object access. It uses policy, reservations, and usage tracking so teams can protect shared capacity while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The platform engineering team used Storage Resource Quota when the workload read a large dataset, so the team could protect shared capacity before the workload scaled up.”
Brouillon de traduction automatique (French) 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.
“Exemple en brouillon: 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.”
Brouillon de traduction automatique (French) for "Scheduler Runtime Profile": Scheduler Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for placement of work onto resources. It uses sampling, traces, and resource metrics so teams can target optimization work while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The platform engineering team used Scheduler Runtime Profile when the cluster needed to place a job, so the team could target optimization work before the workload scaled up.”
Brouillon de traduction automatique (French) for "Scheduler Checkpoint Restore": Scheduler Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for placement of work onto resources. 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.
“Exemple en brouillon: The platform engineering team used Scheduler Checkpoint Restore when the cluster needed to place a job, so the team could recover long-running work before the workload scaled up.”
Brouillon de traduction automatique (French) 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.
“Exemple en brouillon: 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.”
Brouillon de traduction automatique (French) 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.
“Exemple en brouillon: 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.”
Brouillon de traduction automatique (French) for "GPU Isolation Boundary": GPU Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for accelerated compute for parallel workloads. It uses namespaces, sandboxes, and access controls so teams can reduce cross-workload risk while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The platform engineering team used GPU Isolation Boundary when the training job requested more memory, so the team could reduce cross-workload risk before the workload scaled up.”
Brouillon de traduction automatique (French) for "Infrastructure Build Gate": Infrastructure Build Gate is a devops quality gate that blocks promotion when required checks fail for cloud resources and platform wiring. 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.
“Exemple en brouillon: The DevOps team used Infrastructure Build Gate when a new region was added, so the team could prevent broken releases before the deployment window opened.”