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.
Rascunho de traducao automatica (Portuguese) for "Identity Evidence Chain": Identity Evidence Chain is a security audit record that preserves how security evidence was collected and handled for user and workload identity. It uses timestamps, hashes, owners, and storage controls so teams can support trustworthy investigation while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The security team used Identity Evidence Chain when a service account requested access, so the team could support trustworthy investigation before the risk review began.”
Rascunho de traducao automatica (Portuguese) for "Memory Isolation Boundary": Memory Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for volatile runtime storage. 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 Memory Isolation Boundary when the process approached its memory limit, so the team could reduce cross-workload risk before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Service Mesh Egress Policy": Service Mesh Egress Policy is a networking outbound control that decides where workloads may send traffic for east-west service communication. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The network engineering team used Service Mesh Egress Policy when a service called another service, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”
Rascunho de traducao automatica (Portuguese) for "Satellite Link Budget": Satellite Link Budget is a space planning model that estimates whether a signal path has enough margin for reliable communication for commercial and civil satellite service delivery. It uses antenna gain, path loss, modulation, and noise estimates so teams can schedule contacts with realistic margins while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The mission team used Satellite Link Budget when the constellation shifted traffic between spacecraft, so the team could schedule contacts with realistic margins before the next mission decision point.”
Rascunho de traducao automatica (Portuguese) for "Service Mesh Anycast Endpoint": Service Mesh Anycast Endpoint is a networking routing pattern that advertises one address from multiple locations for east-west service communication. 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 Service Mesh Anycast Endpoint when a service called another service, so the team could serve users from nearby healthy sites before traffic crossed a service boundary.”
Rascunho de traducao automatica (Portuguese) for "Packet Rate Limit": Packet Rate Limit is a networking traffic control that caps request volume over a period for unit of network transmission. It uses identity keys, windows, and response policies so teams can protect services from overload while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The network engineering team used Packet Rate Limit when packet loss increased, so the team could protect services from overload before traffic crossed a service boundary.”
Rascunho de traducao automatica (Portuguese) for "Environment Approval Step": Environment Approval Step is a devops workflow control that requires review before a sensitive change proceeds for configuration for a runtime stage. 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 Environment Approval Step when staging and production drifted, so the team could keep high-risk automation accountable before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Memory Image Hardening": Memory Image Hardening is a compute security practice that reduces risk inside packaged runtime images for volatile runtime storage. 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 Memory Image Hardening when the process approached its memory limit, so the team could ship safer workloads before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Scheduler Isolation Boundary": Scheduler Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for placement of work onto resources. 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 Scheduler Isolation Boundary when the cluster needed to place a job, so the team could reduce cross-workload risk before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Storage Runtime Profile": Storage Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for persistent data and object access. 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 Storage Runtime Profile when the workload read a large dataset, so the team could target optimization work before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Container Checkpoint Restore": Container Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for packaged application runtime. It uses snapshots, state files, and integrity checks so teams can recover long-running work while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The platform engineering team used Container Checkpoint Restore when the image started on a new node, so the team could recover long-running work before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Inference Agent Trace": Inference Agent Trace is a ai observability record that captures the steps an AI workflow took for model execution for user or system requests. 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.
“Exemplo em rascunho: The AI platform team used Inference Agent Trace when the inference route moved to a faster region, so the team could debug agent behavior without exposing secrets before the agent workflow reached production.”
Rascunho de traducao automatica (Portuguese) for "Serverless Cold Start Budget": Serverless Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for event-driven function execution. 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 Serverless Cold Start Budget when the function received a traffic burst, so the team could keep first requests responsive before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Edge Workload Priority": Edge Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for globally distributed runtime. 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 Edge Workload Priority when the request arrived near a user, so the team could protect critical paths before the workload scaled up.”
Rascunho de traducao automatica (Portuguese) for "Environment Release Manifest": Environment Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for configuration for a runtime stage. 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 Environment Release Manifest when staging and production drifted, so the team could make releases auditable before the deployment window opened.”
Rascunho de traducao automatica (Portuguese) for "Packet Health Probe": Packet Health Probe is a networking availability check that tests whether a service or path can receive traffic for unit of network transmission. 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 Packet Health Probe when packet loss increased, so the team could send traffic only to healthy targets before traffic crossed a service boundary.”
Rascunho de traducao automatica (Portuguese) for "Telemetry Science Window": Telemetry Science Window is a space planning interval that marks when conditions are suitable for data collection for spacecraft health and performance monitoring. It uses target visibility, power budgets, thermal state, and downlink availability so teams can capture useful observations without breaking constraints while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The mission team used Telemetry Science Window when the telemetry stream showed unexpected drift, so the team could capture useful observations without breaking constraints before the next mission decision point.”
Rascunho de traducao automatica (Portuguese) for "Telemetry Thermal Margin": Telemetry Thermal Margin is a space safety metric that tracks how much temperature headroom remains before a component exceeds limits for spacecraft health and performance monitoring. It uses sensor data, heat models, and operational constraints so teams can protect hardware during changing conditions while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The mission team used Telemetry Thermal Margin when the telemetry stream showed unexpected drift, so the team could protect hardware during changing conditions before the next mission decision point.”
Rascunho de traducao automatica (Portuguese) for "Mission Control Command Sequence": Mission Control Command Sequence is a space operations artifact that orders spacecraft actions into a validated timeline for flight control room coordination. It uses syntax checks, dependency rules, and simulation so teams can send instructions without hidden conflicts while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The mission team used Mission Control Command Sequence when the operations console detected a constraint, so the team could send instructions without hidden conflicts before the next mission decision point.”
Rascunho de traducao automatica (Portuguese) for "Storage Isolation Boundary": Storage Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for persistent data and object access. 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 Storage Isolation Boundary when the workload read a large dataset, so the team could reduce cross-workload risk before the workload scaled up.”