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 "Incident Rollout Guard": Incident Rollout Guard is a devops release control that limits exposure during gradual deployment for response to service degradation. 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 Incident Rollout Guard when on-call received a high-severity page, so the team could reduce blast radius before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "CPU Runtime Profile": CPU Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for general-purpose processor scheduling. 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 CPU Runtime Profile when the service hit a compute ceiling, so the team could target optimization work before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Secret Approval Step": Secret Approval Step is a devops workflow control that requires review before a sensitive change proceeds for credential and sensitive configuration. It uses role checks, comments, and audit logs so teams can keep high-risk automation accountable while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The DevOps team used Secret Approval Step when a token rotated, so the team could keep high-risk automation accountable before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Infrastructure Secret Rotation": Infrastructure Secret Rotation is a devops credential workflow that replaces sensitive keys without service interruption for cloud resources and platform wiring. It uses dual credentials, rollout steps, and revocation so teams can reduce credential exposure while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The DevOps team used Infrastructure Secret Rotation when a new region was added, so the team could reduce credential exposure before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Cache Backpressure Control": Cache Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for fast temporary data layer. It uses queues, retry budgets, and admission control so teams can avoid overload cascades while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The platform engineering team used Cache Backpressure Control when the cache missed during peak traffic, so the team could avoid overload cascades before the workload scaled up.”
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 "Serverless Isolation Boundary": Serverless Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for event-driven function execution. 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 Serverless Isolation Boundary when the function received a traffic burst, so the team could reduce cross-workload risk before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Cache Autoscaling Policy": Cache Autoscaling Policy is a compute control loop that changes capacity based on demand signals for fast temporary data layer. It uses metrics, thresholds, and cooldowns so teams can match resources to load while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The platform engineering team used Cache Autoscaling Policy when the cache missed during peak traffic, so the team could match resources to load before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Release Artifact Signature": Release Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for versioned delivery of code or content. It uses cryptographic signatures, provenance, and verification so teams can trust deployed packages while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The DevOps team used Release Artifact Signature when the release notes were generated, so the team could trust deployed packages before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "BGP Certificate Monitor": BGP Certificate Monitor is a networking security monitor that tracks certificate validity and configuration for interdomain routing. It uses expiry checks, chain validation, and alerting so teams can avoid trust failures while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The network engineering team used BGP Certificate Monitor when a route advertisement changed, so the team could avoid trust failures before traffic crossed a service boundary.”