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 "DNS Failover Policy": DNS Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for name resolution and delegation. 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.
“Beispielentwurf: The network engineering team used DNS Failover Policy when a resolver returned stale data, so the team could recover from outages predictably before traffic crossed a service boundary.”
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 "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.
“Beispielentwurf: 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.”
Automatischer Uebersetzungsentwurf (German) for "Memory Autoscaling Policy": Memory Autoscaling Policy is a compute control loop that changes capacity based on demand signals for volatile runtime storage. It uses metrics, thresholds, and cooldowns so teams can match resources to load while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Memory Autoscaling Policy when the process approached its memory limit, so the team could match resources to load before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "TLS Health Probe": TLS Health Probe is a networking availability check that tests whether a service or path can receive traffic for encrypted transport setup. It uses timed requests, thresholds, and regional checks so teams can send traffic only to healthy targets while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The network engineering team used TLS Health Probe when a certificate neared expiration, so the team could send traffic only to healthy targets before traffic crossed a service boundary.”
Automatischer Uebersetzungsentwurf (German) for "Infrastructure Artifact Signature": Infrastructure Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for cloud resources and platform wiring. 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 Infrastructure Artifact Signature when a new region was added, so the team could trust deployed packages before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Memory Checkpoint Restore": Memory Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for volatile runtime storage. 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 Memory Checkpoint Restore when the process approached its memory limit, so the team could recover long-running work before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) 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.
“Beispielentwurf: 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.”
Automatischer Uebersetzungsentwurf (German) for "Scheduler Cache Invalidation": Scheduler Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for placement of work onto resources. It uses keys, tags, timestamps, and purge events so teams can serve current results while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Scheduler Cache Invalidation when the cluster needed to place a job, so the team could serve current results before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Container Backpressure Control": Container Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for packaged application runtime. It uses queues, retry budgets, and admission control so teams can avoid overload cascades while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Container Backpressure Control when the image started on a new node, so the team could avoid overload cascades before the workload scaled up.”