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 Image Hardening": Serverless Image Hardening is a compute security practice that reduces risk inside packaged runtime images for event-driven function execution. It uses minimal bases, patching, and vulnerability checks so teams can ship safer workloads while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The platform engineering team used Serverless Image Hardening when the function received a traffic burst, so the team could ship safer workloads before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Secret Secret Rotation": Secret Secret Rotation is a devops credential workflow that replaces sensitive keys without service interruption for credential and sensitive configuration. 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 Secret Secret Rotation when a token rotated, so the team could reduce credential exposure before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Runbook Runbook Check": Runbook Runbook Check is a devops operational test that confirms that documented procedures still work for documented operational procedure. 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.
“Exemplo em rascunho: The DevOps team used Runbook Runbook Check when a responder needed the recovery steps, so the team could keep response playbooks current before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "DNS Path Trace": DNS Path Trace is a networking diagnostic record that shows where traffic travels and where delay or loss appears for name resolution and delegation. It uses hop data, timing, and network metadata so teams can debug connectivity issues while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The network engineering team used DNS Path Trace when a resolver returned stale data, so the team could debug connectivity issues before traffic crossed a service boundary.”
Rascunho de traducao automatica (Portuguese) 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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) for "Release Release Manifest": Release Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for versioned delivery of code or content. 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 Release Release Manifest when the release notes were generated, so the team could make releases auditable before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "TLS Path Trace": TLS Path Trace is a networking diagnostic record that shows where traffic travels and where delay or loss appears for encrypted transport setup. It uses hop data, timing, and network metadata so teams can debug connectivity issues while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The network engineering team used TLS Path Trace when a certificate neared expiration, so the team could debug connectivity issues before traffic crossed a service boundary.”
Rascunho de traducao automatica (Portuguese) for "Incident Artifact Signature": Incident Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for response to service degradation. 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 Incident Artifact Signature when on-call received a high-severity page, so the team could trust deployed packages before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "DNS Anycast Endpoint": DNS Anycast Endpoint is a networking routing pattern that advertises one address from multiple locations for name resolution and delegation. It uses regional announcements, health checks, and traffic steering so teams can serve users from nearby healthy sites while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The network engineering team used DNS Anycast Endpoint when a resolver returned stale data, so the team could serve users from nearby healthy sites before traffic crossed a service boundary.”
Rascunho de traducao automatica (Portuguese) for "Container Backpressure Control": Container Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for packaged application runtime. 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 Container Backpressure Control when the image started on a new node, so the team could avoid overload cascades before the workload scaled up.”