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
Cache Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for fast temporary data layer. 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 Cache Isolation Boundary when the cache missed during peak traffic, so the team could reduce cross-workload risk before the workload scaled up.”
Runbook Rollback Plan is a devops recovery plan that defines how to return to a known good version for documented operational procedure. It uses version pins, database notes, and operator steps so teams can recover quickly from bad changes while keeping evidence, reliability, and public-safe operational boundaries clear.
“The DevOps team used Runbook Rollback Plan when a responder needed the recovery steps, so the team could recover quickly from bad changes before the deployment window opened.”
CPU Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for general-purpose processor scheduling. 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 CPU Cache Invalidation when the service hit a compute ceiling, so the team could serve current results before the workload scaled up.”
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.”
Incident Incident Timeline is a devops response record that orders alerts, actions, and decisions during an incident for response to service degradation. 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 Incident Incident Timeline when on-call received a high-severity page, so the team could learn from outages without guesswork before the deployment window opened.”
Container Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for packaged application runtime. 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 Container Backpressure Control when the image started on a new node, so the team could avoid overload cascades before the workload scaled up.”
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.”
TLS Packet Capture is a networking diagnostic artifact that records network packets for analysis for encrypted transport setup. 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.
“The network engineering team used TLS Packet Capture when a certificate neared expiration, so the team could investigate protocol behavior safely before traffic crossed a service boundary.”
TLS Egress Policy is a networking outbound control that decides where workloads may send traffic for encrypted transport setup. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.
“The network engineering team used TLS Egress Policy when a certificate neared expiration, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”
Queue Image Hardening is a compute security practice that reduces risk inside packaged runtime images for asynchronous work buffer. It uses minimal bases, patching, and vulnerability checks so teams can ship safer workloads while keeping evidence, reliability, and public-safe operational boundaries clear.
“The platform engineering team used Queue Image Hardening when the queue depth increased, so the team could ship safer workloads before the workload scaled up.”