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 "DNS Ingress Rule": DNS Ingress Rule is a networking boundary rule that controls how external traffic enters a service for name resolution and delegation. 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.
“مسودة مثال: The network engineering team used DNS Ingress Rule when a resolver returned stale data, so the team could keep entry points predictable before traffic crossed a service boundary.”
مسودة ترجمة بمساعدة آلية (Arabic) for "Cache Backpressure Control": Cache Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for fast temporary data layer. 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 Cache Backpressure Control when the cache missed during peak traffic, 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 "Container Isolation Boundary": Container Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for packaged application runtime. 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 Container Isolation Boundary when the image started on a new node, so the team could reduce cross-workload risk before the workload scaled up.”
مسودة ترجمة بمساعدة آلية (Arabic) for "Incident Release Manifest": Incident Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for response to service degradation. It uses commit IDs, checksums, and deployment URLs so teams can make releases auditable while keeping evidence, reliability, and public-safe operational boundaries clear.
“مسودة مثال: The DevOps team used Incident Release Manifest when on-call received a high-severity page, so the team could make releases auditable before the deployment window opened.”
مسودة ترجمة بمساعدة آلية (Arabic) 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.
“مسودة مثال: 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.”
مسودة ترجمة بمساعدة آلية (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 "Runbook Incident Timeline": Runbook Incident Timeline is a devops response record that orders alerts, actions, and decisions during an incident for documented operational procedure. It uses timestamps, owners, and evidence links so teams can learn from outages without guesswork while keeping evidence, reliability, and public-safe operational boundaries clear.
“مسودة مثال: The DevOps team used Runbook Incident Timeline when a responder needed the recovery steps, so the team could learn from outages without guesswork before the deployment window opened.”
مسودة ترجمة بمساعدة آلية (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 "Queue Backpressure Control": Queue Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for asynchronous work buffer. 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 Queue Backpressure Control when the queue depth increased, so the team could avoid overload cascades before the workload scaled up.”