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
Rascunho de traducao automatica (Portuguese) 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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) for "Observability Rollback Plan": Observability Rollback Plan is a devops recovery plan that defines how to return to a known good version for logs, metrics, traces, and events. 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.
“Exemplo em rascunho: The DevOps team used Observability Rollback Plan when latency increased after deploy, so the team could recover quickly from bad changes before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Container Cache Invalidation": Container Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for packaged application runtime. It uses keys, tags, timestamps, and purge events so teams can serve current results while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The platform engineering team used Container Cache Invalidation when the image started on a new node, so the team could serve current results before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Release Incident Timeline": Release Incident Timeline is a devops response record that orders alerts, actions, and decisions during an incident for versioned delivery of code or content. 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.
“Exemplo em rascunho: The DevOps team used Release Incident Timeline when the release notes were generated, so the team could learn from outages without guesswork before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "GPU Placement Strategy": GPU Placement Strategy is a compute scheduling rule that chooses where workloads should run for accelerated compute for parallel workloads. It uses affinity, topology, availability, and cost signals so teams can improve reliability and efficiency while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The platform engineering team used GPU Placement Strategy when the training job requested more memory, so the team could improve reliability and efficiency before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Runbook Infra Plan": Runbook Infra Plan is a devops change preview that shows expected infrastructure changes before apply for documented operational procedure. 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.
“Exemplo em rascunho: The DevOps team used Runbook Infra Plan when a responder needed the recovery steps, so the team could review platform changes safely before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Queue Cold Start Budget": Queue Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for asynchronous work buffer. 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.
“Exemplo em rascunho: The platform engineering team used Queue Cold Start Budget when the queue depth increased, so the team could keep first requests responsive before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) 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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) 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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) for "Incident Release Manifest": Incident Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for response to service degradation. It uses commit IDs, checksums, and deployment URLs so teams can make releases auditable while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The DevOps team used Incident Release Manifest when on-call received a high-severity page, so the team could make releases auditable before the deployment window opened.”