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
Brouillon de traduction automatique (French) for "Container Autoscaling Policy": Container Autoscaling Policy is a compute control loop that changes capacity based on demand signals for packaged application runtime. It uses metrics, thresholds, and cooldowns so teams can match resources to load while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The platform engineering team used Container Autoscaling Policy when the image started on a new node, so the team could match resources to load before the workload scaled up.”
Brouillon de traduction automatique (French) for "Edge Cache Invalidation": Edge Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for globally distributed runtime. It uses keys, tags, timestamps, and purge events so teams can serve current results while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The platform engineering team used Edge Cache Invalidation when the request arrived near a user, so the team could serve current results before the workload scaled up.”
Brouillon de traduction automatique (French) for "Queue Placement Strategy": Queue Placement Strategy is a compute scheduling rule that chooses where workloads should run for asynchronous work buffer. 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 Queue Placement Strategy when the queue depth increased, so the team could improve reliability and efficiency before the workload scaled up.”
Brouillon de traduction automatique (French) 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.
“Exemple en brouillon: 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.”
Brouillon de traduction automatique (French) 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.
“Exemple en brouillon: 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.”
Brouillon de traduction automatique (French) for "Infrastructure Infra Plan": Infrastructure Infra Plan is a devops change preview that shows expected infrastructure changes before apply for cloud resources and platform wiring. It uses resource graphs, policy checks, and cost notes so teams can review platform changes safely while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The DevOps team used Infrastructure Infra Plan when a new region was added, so the team could review platform changes safely before the deployment window opened.”
Brouillon de traduction automatique (French) for "BGP Failover Policy": BGP Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for interdomain routing. 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 BGP Failover Policy when a route advertisement changed, so the team could recover from outages predictably before traffic crossed a service boundary.”
Brouillon de traduction automatique (French) for "Scheduler Workload Priority": Scheduler Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for placement of work onto resources. 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 Scheduler Workload Priority when the cluster needed to place a job, so the team could protect critical paths before the workload scaled up.”
Brouillon de traduction automatique (French) for "Cache Resource Quota": Cache Resource Quota is a compute limit that sets how much compute a workload may consume for fast temporary data layer. 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 Cache Resource Quota when the cache missed during peak traffic, so the team could protect shared capacity before the workload scaled up.”
Brouillon de traduction automatique (French) for "Queue Cold Start Budget": Queue Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for asynchronous work buffer. 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.
“Exemple en brouillon: The platform engineering team used Queue Cold Start Budget when the queue depth increased, so the team could keep first requests responsive before the workload scaled up.”