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
مسودة ترجمة بمساعدة آلية (Arabic) 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.
“مسودة مثال: 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.”
مسودة ترجمة بمساعدة آلية (Arabic) for "GPU Checkpoint Restore": GPU Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for accelerated compute for parallel workloads. 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.
“مسودة مثال: The platform engineering team used GPU Checkpoint Restore when the training job requested more memory, so the team could recover long-running work before the workload scaled up.”
مسودة ترجمة بمساعدة آلية (Arabic) for "Infrastructure Trace Link": Infrastructure Trace Link is a devops observability link that connects a deployment or workflow to runtime evidence for cloud resources and platform wiring. It uses trace IDs, span metadata, and release identifiers so teams can debug production changes faster while keeping evidence, reliability, and public-safe operational boundaries clear.
“مسودة مثال: The DevOps team used Infrastructure Trace Link when a new region was added, so the team could debug production changes faster before the deployment window opened.”
مسودة ترجمة بمساعدة آلية (Arabic) 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.
“مسودة مثال: 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.”
مسودة ترجمة بمساعدة آلية (Arabic) for "Serverless Backpressure Control": Serverless Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for event-driven function execution. It uses queues, retry budgets, and admission control so teams can avoid overload cascades while keeping evidence, reliability, and public-safe operational boundaries clear.
“مسودة مثال: The platform engineering team used Serverless Backpressure Control when the function received a traffic burst, so the team could avoid overload cascades before the workload scaled up.”
مسودة ترجمة بمساعدة آلية (Arabic) for "TLS Health Probe": TLS Health Probe is a networking availability check that tests whether a service or path can receive traffic for encrypted transport setup. 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.
“مسودة مثال: The network engineering team used TLS Health Probe when a certificate neared expiration, so the team could send traffic only to healthy targets before traffic crossed a service boundary.”
مسودة ترجمة بمساعدة آلية (Arabic) for "Serverless Cache Invalidation": Serverless Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for event-driven function execution. It uses keys, tags, timestamps, and purge events so teams can serve current results while keeping evidence, reliability, and public-safe operational boundaries clear.
“مسودة مثال: The platform engineering team used Serverless Cache Invalidation when the function received a traffic burst, so the team could serve current results before the workload scaled up.”
مسودة ترجمة بمساعدة آلية (Arabic) for "Storage Backpressure Control": Storage Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for persistent data and object access. It uses queues, retry budgets, and admission control so teams can avoid overload cascades while keeping evidence, reliability, and public-safe operational boundaries clear.
“مسودة مثال: The platform engineering team used Storage Backpressure Control when the workload read a large dataset, so the team could avoid overload cascades before the workload scaled up.”
مسودة ترجمة بمساعدة آلية (Arabic) for "Memory Autoscaling Policy": Memory Autoscaling Policy is a compute control loop that changes capacity based on demand signals for volatile runtime storage. It uses metrics, thresholds, and cooldowns so teams can match resources to load while keeping evidence, reliability, and public-safe operational boundaries clear.
“مسودة مثال: The platform engineering team used Memory Autoscaling Policy when the process approached its memory limit, so the team could match resources to load before the workload scaled up.”
مسودة ترجمة بمساعدة آلية (Arabic) for "DNS Failover Policy": DNS Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for name resolution and delegation. 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.
“مسودة مثال: The network engineering team used DNS Failover Policy when a resolver returned stale data, so the team could recover from outages predictably before traffic crossed a service boundary.”