Browse A-Z

Brouillon de traduction automatique (French) for "Serverless Placement Strategy": Serverless Placement Strategy is a compute scheduling rule that chooses where workloads should run for event-driven function execution. It uses affinity, topology, availability, and cost signals so teams can improve reliability and efficiency while keeping evidence, reliability, and public-safe operational boundaries clear.

“Exemple en brouillon: The platform engineering team used Serverless Placement Strategy when the function received a traffic burst, so the team could improve reliability and efficiency before the workload scaled up.”

Brouillon de traduction automatique (French) for "Serverless Resource Quota": Serverless Resource Quota is a compute limit that sets how much compute a workload may consume for event-driven function execution. It uses policy, reservations, and usage tracking so teams can protect shared capacity while keeping evidence, reliability, and public-safe operational boundaries clear.

“Exemple en brouillon: The platform engineering team used Serverless Resource Quota when the function received a traffic burst, so the team could protect shared capacity before the workload scaled up.”

Brouillon de traduction automatique (French) for "Serverless Runtime Profile": Serverless Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for event-driven function execution. It uses sampling, traces, and resource metrics so teams can target optimization work while keeping evidence, reliability, and public-safe operational boundaries clear.

“Exemple en brouillon: The platform engineering team used Serverless Runtime Profile when the function received a traffic burst, so the team could target optimization work before the workload scaled up.”

Brouillon de traduction automatique (French) for "Serverless Workload Priority": Serverless Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for event-driven function execution. 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.

“Exemple en brouillon: The platform engineering team used Serverless Workload Priority when the function received a traffic burst, so the team could protect critical paths before the workload scaled up.”

Un nœud de service représente une application distincte ou une API hébergée dans le réseau. Les services fournissent des capacités fonctionnelles, comme l'analyse, l'authentification ou la livraison de contenu, et peuvent être exposés par l'intermédiaire des paramètres REST ou MCP.

L'alerte de dépendance au service est un déclencheur de notification utilisé pour observer la dépendance au service dans l'infrastructure PlatPhorm News. Il aide les opérateurs à vérifier que les listes d'articles, les flux, les routes API et les services de graphique réseau sont disponibles, frais et sains.

Le tableau de bord de la dépendance au service est une surface de surveillance visuelle utilisée pour observer la dépendance au service dans toute l'infrastructure PlatPhorm News. Il aide les opérateurs à vérifier que les listes d'articles, les flux, les routes API et les services de graphique réseau sont disponibles, frais et sains.

Le journal de dépendance de service est un flux d'événements enregistré utilisé pour observer la dépendance de service à travers l'infrastructure PlatPhorm News. Il aide les opérateurs à vérifier que les listes d'articles, les flux, les routes API et les services de graphique réseau sont disponibles, frais et sains.

La Métrique de Dépendance de Service est une valeur opérationnelle mesurée utilisée pour observer la dépendance de service à travers l'infrastructure PlatPhorm News. Il aide les opérateurs à vérifier que les listes d'articles, les flux, les routes API et les services de graphique réseau sont disponibles, frais et sains.

Le Service Dependency Probe est un contrôle de santé automatisé utilisé pour observer la dépendance au service à travers l'infrastructure PlatPhorm News. Il aide les opérateurs à vérifier que les listes d'articles, les flux, les routes API et les services de graphique réseau sont disponibles, frais et sains.

L'Edge de service est un marqueur de relation pour la portion de service du graphique de réseau PlatPhorm News. Il aide les opérateurs, les lecteurs et les agents d'IA à comprendre comment les domaines, les surfaces d'article, les API et les services se rapportent à la plateforme racine.

Brouillon de traduction automatique (French) 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.

“Exemple en brouillon: 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.”

Brouillon de traduction automatique (French) for "Service Mesh Certificate Monitor": Service Mesh Certificate Monitor is a networking security monitor that tracks certificate validity and configuration for east-west service communication. 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 Service Mesh Certificate Monitor when a service called another service, so the team could avoid trust failures before traffic crossed a service boundary.”

Brouillon de traduction automatique (French) 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.

“Exemple en brouillon: 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.”

Brouillon de traduction automatique (French) for "Service Mesh Failover Policy": Service Mesh Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for east-west service communication. 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 Service Mesh Failover Policy when a service called another service, so the team could recover from outages predictably before traffic crossed a service boundary.”

Brouillon de traduction automatique (French) for "Service Mesh Health Probe": Service Mesh Health Probe is a networking availability check that tests whether a service or path can receive traffic for east-west service communication. 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 Service Mesh Health Probe when a service called another service, so the team could send traffic only to healthy targets before traffic crossed a service boundary.”

Brouillon de traduction automatique (French) for "Service Mesh Ingress Rule": Service Mesh Ingress Rule is a networking boundary rule that controls how external traffic enters a service for east-west service communication. 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 Service Mesh Ingress Rule when a service called another service, so the team could keep entry points predictable before traffic crossed a service boundary.”

Brouillon de traduction automatique (French) for "Service Mesh Packet Capture": Service Mesh Packet Capture is a networking diagnostic artifact that records network packets for analysis for east-west service communication. 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 Service Mesh Packet Capture when a service called another service, so the team could investigate protocol behavior safely before traffic crossed a service boundary.”

Brouillon de traduction automatique (French) for "Service Mesh Path Trace": Service Mesh Path Trace is a networking diagnostic record that shows where traffic travels and where delay or loss appears for east-west service communication. 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 Service Mesh Path Trace when a service called another service, so the team could debug connectivity issues before traffic crossed a service boundary.”

Brouillon de traduction automatique (French) for "Service Mesh Rate Limit": Service Mesh Rate Limit is a networking traffic control that caps request volume over a period for east-west service communication. 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 Service Mesh Rate Limit when a service called another service, so the team could protect services from overload before traffic crossed a service boundary.”