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 "Storage Checkpoint Restore": Storage Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for persistent data and object access. 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 Storage Checkpoint Restore when the workload read a large dataset, so the team could recover long-running work before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) 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.
“Beispielentwurf: 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.”
Automatischer Uebersetzungsentwurf (German) for "Serverless Resource Quota": Serverless Resource Quota is a compute limit that sets how much compute a workload may consume for event-driven function execution. It uses policy, reservations, and usage tracking so teams can protect shared capacity while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Serverless Resource Quota when the function received a traffic burst, so the team could protect shared capacity before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Observability Config Drift Check": Observability Config Drift Check is a devops consistency check that finds differences between intended and live configuration for logs, metrics, traces, and events. It uses desired state, live state, and diff reports so teams can avoid surprise environment behavior while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The DevOps team used Observability Config Drift Check when latency increased after deploy, so the team could avoid surprise environment behavior before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Runbook Rollback Plan": Runbook Rollback Plan is a devops recovery plan that defines how to return to a known good version for documented operational procedure. It uses version pins, database notes, and operator steps so teams can recover quickly from bad changes while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The DevOps team used Runbook Rollback Plan when a responder needed the recovery steps, so the team could recover quickly from bad changes before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Secret Release Manifest": Secret Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for credential and sensitive configuration. It uses commit IDs, checksums, and deployment URLs so teams can make releases auditable while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The DevOps team used Secret Release Manifest when a token rotated, so the team could make releases auditable before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Memory Backpressure Control": Memory Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for volatile runtime storage. 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 Memory Backpressure Control when the process approached its memory limit, so the team could avoid overload cascades before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) 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.
“Beispielentwurf: 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.”
Automatischer Uebersetzungsentwurf (German) for "Serverless Runtime Profile": Serverless Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for event-driven function execution. It uses sampling, traces, and resource metrics so teams can target optimization work while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Serverless Runtime Profile when the function received a traffic burst, so the team could target optimization work before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Runbook Artifact Signature": Runbook Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for documented operational procedure. 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 Runbook Artifact Signature when a responder needed the recovery steps, so the team could trust deployed packages before the deployment window opened.”