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
Automatischer Uebersetzungsentwurf (German) for "Queue Checkpoint Restore": Queue Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for asynchronous work buffer. 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.
“Beispielentwurf: The platform engineering team used Queue Checkpoint Restore when the queue depth increased, so the team could recover long-running work before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "BGP Ingress Rule": BGP Ingress Rule is a networking boundary rule that controls how external traffic enters a service for interdomain routing. It uses hostnames, paths, protocols, and policy checks so teams can keep entry points predictable while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The network engineering team used BGP Ingress Rule when a route advertisement changed, so the team could keep entry points predictable before traffic crossed a service boundary.”
Automatischer Uebersetzungsentwurf (German) for "Serverless Capacity Forecast": Serverless Capacity Forecast is a compute planning model that estimates future resource needs for event-driven function execution. It uses traffic history, growth assumptions, and utilization trends so teams can avoid surprise shortages while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Serverless Capacity Forecast when the function received a traffic burst, so the team could avoid surprise shortages before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "GPU Checkpoint Restore": GPU Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for accelerated compute for parallel workloads. 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.
“Beispielentwurf: The platform engineering team used GPU Checkpoint Restore when the training job requested more memory, so the team could recover long-running work before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Release Infra Plan": Release Infra Plan is a devops change preview that shows expected infrastructure changes before apply for versioned delivery of code or content. 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.
“Beispielentwurf: The DevOps team used Release Infra Plan when the release notes were generated, so the team could review platform changes safely before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Container Cold Start Budget": Container Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for packaged application runtime. 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.
“Beispielentwurf: The platform engineering team used Container Cold Start Budget when the image started on a new node, so the team could keep first requests responsive before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "DNS Route Leak Guard": DNS Route Leak Guard is a networking routing control that detects and blocks accidental route propagation for name resolution and delegation. It uses prefix filters, validation, and peer policy so teams can protect reachability while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The network engineering team used DNS Route Leak Guard when a resolver returned stale data, so the team could protect reachability before traffic crossed a service boundary.”
Automatischer Uebersetzungsentwurf (German) for "Release Artifact Signature": Release Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for versioned delivery of code or content. It uses cryptographic signatures, provenance, and verification so teams can trust deployed packages while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The DevOps team used Release Artifact Signature when the release notes were generated, so the team could trust deployed packages before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) 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.
“Beispielentwurf: 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.”
Automatischer Uebersetzungsentwurf (German) for "Cluster Isolation Boundary": Cluster Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for group of machines acting as one platform. It uses namespaces, sandboxes, and access controls so teams can reduce cross-workload risk while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Cluster Isolation Boundary when the cluster added a node pool, so the team could reduce cross-workload risk before the workload scaled up.”