Popular
Popular public definitions for this language. If a reviewed translation is missing, Dictionary shows a labeled machine-assisted draft.
Popular public definitions for this language. If a reviewed translation is missing, Dictionary shows a labeled machine-assisted draft.
Automatischer Uebersetzungsentwurf (German) for "Serverless Cache Invalidation": Serverless Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for event-driven function execution. 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 Serverless Cache Invalidation when the function received a traffic burst, so the team could serve current results before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Release Runbook Check": Release Runbook Check is a devops operational test that confirms that documented procedures still work for versioned delivery of code or content. It uses dry runs, screenshots, and command validation so teams can keep response playbooks current while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The DevOps team used Release Runbook Check when the release notes were generated, so the team could keep response playbooks current before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Load Balancer Egress Policy": Load Balancer Egress Policy is a networking outbound control that decides where workloads may send traffic for traffic distribution. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The network engineering team used Load Balancer Egress Policy when traffic shifted between regions, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”
Automatischer Uebersetzungsentwurf (German) for "Threat Intel Phishing Resistance": Threat Intel Phishing Resistance is a security identity control that reduces success of credential theft attacks for external risk and indicator context. It uses passkeys, hardware-backed factors, and origin checks so teams can protect sign-in flows while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The security team used Threat Intel Phishing Resistance when a new campaign indicator appeared, so the team could protect sign-in flows before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Supply Chain Detection Rule": Supply Chain Detection Rule is a security security analytic that matches suspicious behavior or known indicators for dependencies, builds, and artifacts. It uses logs, thresholds, signatures, and behavioral context so teams can surface actionable alerts while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The security team used Supply Chain Detection Rule when a package update arrived, so the team could surface actionable alerts before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "RAG Agent Trace": RAG Agent Trace is a ai observability record that captures the steps an AI workflow took for retrieval-augmented generation pipelines. It uses trace identifiers, tool events, and redacted metadata so teams can debug agent behavior without exposing secrets while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The AI platform team used RAG Agent Trace when the retriever mixed old and new documents, so the team could debug agent behavior without exposing secrets before the agent workflow reached production.”
Automatischer Uebersetzungsentwurf (German) for "Memory Cache Invalidation": Memory Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for volatile runtime storage. 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 Memory Cache Invalidation when the process approached its memory limit, so the team could serve current results before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Runbook Incident Timeline": Runbook Incident Timeline is a devops response record that orders alerts, actions, and decisions during an incident for documented operational procedure. It uses timestamps, owners, and evidence links so teams can learn from outages without guesswork while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The DevOps team used Runbook Incident Timeline when a responder needed the recovery steps, so the team could learn from outages without guesswork before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Supply Chain Data Redaction": Supply Chain Data Redaction is a security privacy control that removes sensitive values before data leaves a protected context for dependencies, builds, and artifacts. It uses field rules, hashing, and safe logging so teams can share evidence without leaking secrets while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The security team used Supply Chain Data Redaction when a package update arrived, so the team could share evidence without leaking secrets before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Storage Cold Start Budget": Storage Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for persistent data and object access. 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 Storage Cold Start Budget when the workload read a large dataset, so the team could keep first requests responsive before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Orbital Recovery Mode": Orbital Recovery Mode is a space resilience pattern that moves a spacecraft or mission system into a known safe operating state for spacecraft orbit planning and station keeping. It uses health checks, fallback commands, and restart procedures so teams can restore control after anomalies while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The mission team used Orbital Recovery Mode when a spacecraft entered a crowded orbital shell, so the team could restore control after anomalies before the next mission decision point.”
Automatischer Uebersetzungsentwurf (German) for "Secret Rollback Plan": Secret Rollback Plan is a devops recovery plan that defines how to return to a known good version for credential and sensitive configuration. 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 Secret Rollback Plan when a token rotated, so the team could recover quickly from bad changes before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Queue Resource Quota": Queue Resource Quota is a compute limit that sets how much compute a workload may consume for asynchronous work buffer. 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 Queue Resource Quota when the queue depth increased, so the team could protect shared capacity before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Observability Artifact Signature": Observability Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for logs, metrics, traces, and events. 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 Observability Artifact Signature when latency increased after deploy, so the team could trust deployed packages before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Context Agent Trace": Context Agent Trace is a ai observability record that captures the steps an AI workflow took for runtime memory and retrieved information. It uses trace identifiers, tool events, and redacted metadata so teams can debug agent behavior without exposing secrets while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The AI platform team used Context Agent Trace when the context window filled with mixed sources, so the team could debug agent behavior without exposing secrets before the agent workflow reached production.”
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 "QED": QED is listed by Polymaths as a notable work associated with Richard Feynman, connecting that figure's public legacy to Physics, Mathematics, Education.
“Beispielentwurf: QED appears in the Polymaths profile for Richard Feynman.”
Automatischer Uebersetzungsentwurf (German) for "Container Resource Quota": Container Resource Quota is a compute limit that sets how much compute a workload may consume for packaged application runtime. 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 Container Resource Quota when the image started on a new node, so the team could protect shared capacity before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Knowledge Integration Development Practice: Practice metaphorical thinking across disciplines": A recommended development practice for Knowledge Integration: Practice metaphorical thinking across disciplines.
“Beispielentwurf: Polymaths recommends this practice as a concrete way to build knowledge integration.”
Automatischer Uebersetzungsentwurf (German) for "Subnet Certificate Monitor": Subnet Certificate Monitor is a networking security monitor that tracks certificate validity and configuration for address segmentation. It uses expiry checks, chain validation, and alerting so teams can avoid trust failures while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The network engineering team used Subnet Certificate Monitor when a workload moved networks, so the team could avoid trust failures before traffic crossed a service boundary.”