Aller au contenu

Recent

Newest approved public definitions for this language.

/
2,337 source-backed termsdatabase

Brouillon de traduction automatique (French) for "Latency Anycast Endpoint": Latency Anycast Endpoint is a networking routing pattern that advertises one address from multiple locations for time between request and response. 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.

Exemple en brouillon: The network engineering team used Latency Anycast Endpoint when a user saw slow responses, so the team could serve users from nearby healthy sites before traffic crossed a service boundary.

Brouillon de traduction automatique (French) for "Latency Certificate Monitor": Latency Certificate Monitor is a networking security monitor that tracks certificate validity and configuration for time between request and response. It uses expiry checks, chain validation, and alerting so teams can avoid trust failures while keeping evidence, reliability, and public-safe operational boundaries clear.

Exemple en brouillon: The network engineering team used Latency Certificate Monitor when a user saw slow responses, so the team could avoid trust failures before traffic crossed a service boundary.

Brouillon de traduction automatique (French) for "Latency Egress Policy": Latency Egress Policy is a networking outbound control that decides where workloads may send traffic for time between request and response. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.

Exemple en brouillon: The network engineering team used Latency Egress Policy when a user saw slow responses, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.

Brouillon de traduction automatique (French) for "Latency Failover Policy": Latency Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for time between request and response. It uses health signals, priorities, and cooldown windows so teams can recover from outages predictably while keeping evidence, reliability, and public-safe operational boundaries clear.

Exemple en brouillon: The network engineering team used Latency Failover Policy when a user saw slow responses, so the team could recover from outages predictably before traffic crossed a service boundary.

Brouillon de traduction automatique (French) for "Latency Health Probe": Latency Health Probe is a networking availability check that tests whether a service or path can receive traffic for time between request and response. 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.

Exemple en brouillon: The network engineering team used Latency Health Probe when a user saw slow responses, so the team could send traffic only to healthy targets before traffic crossed a service boundary.

Brouillon de traduction automatique (French) for "Latency Ingress Rule": Latency Ingress Rule is a networking boundary rule that controls how external traffic enters a service for time between request and response. 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.

Exemple en brouillon: The network engineering team used Latency Ingress Rule when a user saw slow responses, so the team could keep entry points predictable before traffic crossed a service boundary.

Brouillon de traduction automatique (French) for "Latency Packet Capture": Latency Packet Capture is a networking diagnostic artifact that records network packets for analysis for time between request and response. It uses bounded capture windows, filters, and redaction so teams can investigate protocol behavior safely while keeping evidence, reliability, and public-safe operational boundaries clear.

Exemple en brouillon: The network engineering team used Latency Packet Capture when a user saw slow responses, so the team could investigate protocol behavior safely before traffic crossed a service boundary.

Brouillon de traduction automatique (French) for "Latency Path Trace": Latency Path Trace is a networking diagnostic record that shows where traffic travels and where delay or loss appears for time between request and response. It uses hop data, timing, and network metadata so teams can debug connectivity issues while keeping evidence, reliability, and public-safe operational boundaries clear.

Exemple en brouillon: The network engineering team used Latency Path Trace when a user saw slow responses, so the team could debug connectivity issues before traffic crossed a service boundary.

Brouillon de traduction automatique (French) for "Latency Resolver Cache": Latency Resolver Cache is a networking performance layer that stores DNS answers for reuse until they expire for time between request and response. It uses TTL rules, cache keys, and invalidation so teams can reduce lookup latency while keeping evidence, reliability, and public-safe operational boundaries clear.

Exemple en brouillon: The network engineering team used Latency Resolver Cache when a user saw slow responses, so the team could reduce lookup latency before traffic crossed a service boundary.

Brouillon de traduction automatique (French) for "Latency Route Leak Guard": Latency Route Leak Guard is a networking routing control that detects and blocks accidental route propagation for time between request and response. It uses prefix filters, validation, and peer policy so teams can protect reachability while keeping evidence, reliability, and public-safe operational boundaries clear.

Exemple en brouillon: The network engineering team used Latency Route Leak Guard when a user saw slow responses, so the team could protect reachability before traffic crossed a service boundary.

Brouillon de traduction automatique (French) for "Latency Traffic Shaper": Latency Traffic Shaper is a networking control mechanism that limits or prioritizes flows across links for time between request and response. It uses queues, rate limits, and quality-of-service rules so teams can protect important traffic while keeping evidence, reliability, and public-safe operational boundaries clear.

Exemple en brouillon: The network engineering team used Latency Traffic Shaper when a user saw slow responses, so the team could protect important traffic before traffic crossed a service boundary.

Brouillon de traduction automatique (French) for "Load Balancer Anycast Endpoint": Load Balancer Anycast Endpoint is a networking routing pattern that advertises one address from multiple locations for traffic distribution. 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.

Exemple en brouillon: The network engineering team used Load Balancer Anycast Endpoint when traffic shifted between regions, so the team could serve users from nearby healthy sites before traffic crossed a service boundary.

Brouillon de traduction automatique (French) for "Load Balancer Certificate Monitor": Load Balancer Certificate Monitor is a networking security monitor that tracks certificate validity and configuration for traffic distribution. It uses expiry checks, chain validation, and alerting so teams can avoid trust failures while keeping evidence, reliability, and public-safe operational boundaries clear.

Exemple en brouillon: The network engineering team used Load Balancer Certificate Monitor when traffic shifted between regions, so the team could avoid trust failures before traffic crossed a service boundary.

Brouillon de traduction automatique (French) for "Load Balancer Egress Policy": Load Balancer Egress Policy is a networking outbound control that decides where workloads may send traffic for traffic distribution. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.

Exemple en brouillon: The network engineering team used Load Balancer Egress Policy when traffic shifted between regions, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.

Brouillon de traduction automatique (French) for "Load Balancer Failover Policy": Load Balancer Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for traffic distribution. It uses health signals, priorities, and cooldown windows so teams can recover from outages predictably while keeping evidence, reliability, and public-safe operational boundaries clear.

Exemple en brouillon: The network engineering team used Load Balancer Failover Policy when traffic shifted between regions, so the team could recover from outages predictably before traffic crossed a service boundary.

Brouillon de traduction automatique (French) for "Load Balancer Health Probe": Load Balancer Health Probe is a networking availability check that tests whether a service or path can receive traffic for traffic distribution. 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.

Exemple en brouillon: The network engineering team used Load Balancer Health Probe when traffic shifted between regions, so the team could send traffic only to healthy targets before traffic crossed a service boundary.

Brouillon de traduction automatique (French) for "Load Balancer Ingress Rule": Load Balancer Ingress Rule is a networking boundary rule that controls how external traffic enters a service for traffic distribution. 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.

Exemple en brouillon: The network engineering team used Load Balancer Ingress Rule when traffic shifted between regions, so the team could keep entry points predictable before traffic crossed a service boundary.

Brouillon de traduction automatique (French) for "Load Balancer Packet Capture": Load Balancer Packet Capture is a networking diagnostic artifact that records network packets for analysis for traffic distribution. It uses bounded capture windows, filters, and redaction so teams can investigate protocol behavior safely while keeping evidence, reliability, and public-safe operational boundaries clear.

Exemple en brouillon: The network engineering team used Load Balancer Packet Capture when traffic shifted between regions, so the team could investigate protocol behavior safely before traffic crossed a service boundary.

Brouillon de traduction automatique (French) for "Load Balancer Path Trace": Load Balancer Path Trace is a networking diagnostic record that shows where traffic travels and where delay or loss appears for traffic distribution. It uses hop data, timing, and network metadata so teams can debug connectivity issues while keeping evidence, reliability, and public-safe operational boundaries clear.

Exemple en brouillon: The network engineering team used Load Balancer Path Trace when traffic shifted between regions, so the team could debug connectivity issues before traffic crossed a service boundary.

Brouillon de traduction automatique (French) for "Load Balancer Rate Limit": Load Balancer Rate Limit is a networking traffic control that caps request volume over a period for traffic distribution. 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.

Exemple en brouillon: The network engineering team used Load Balancer Rate Limit when traffic shifted between regions, so the team could protect services from overload before traffic crossed a service boundary.