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 "Infrastructure Release Manifest": Infrastructure Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for cloud resources and platform wiring. 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 Infrastructure Release Manifest when a new region was added, so the team could make releases auditable before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Release Rollout Guard": Release Rollout Guard is a devops release control that limits exposure during gradual deployment for versioned delivery of code or content. It uses traffic slices, health checks, and automatic pause rules so teams can reduce blast radius while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The DevOps team used Release Rollout Guard when the release notes were generated, so the team could reduce blast radius before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) 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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) for "Memory Workload Priority": Memory Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for volatile runtime storage. 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.
“Exemplo em rascunho: The platform engineering team used Memory Workload Priority when the process approached its memory limit, so the team could protect critical paths before the workload scaled up.”
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 "GPU Runtime Profile": GPU Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for accelerated compute for parallel workloads. It uses sampling, traces, and resource metrics so teams can target optimization work while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The platform engineering team used GPU Runtime Profile when the training job requested more memory, so the team could target optimization work before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Container Isolation Boundary": Container Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for packaged application runtime. It uses namespaces, sandboxes, and access controls so teams can reduce cross-workload risk while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The platform engineering team used Container Isolation Boundary when the image started on a new node, so the team could reduce cross-workload risk before the workload scaled up.”
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 "Queue Isolation Boundary": Queue Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for asynchronous work buffer. It uses namespaces, sandboxes, and access controls so teams can reduce cross-workload risk while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The platform engineering team used Queue Isolation Boundary when the queue depth increased, so the team could reduce cross-workload risk before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) 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.
“Exemplo em rascunho: 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.”