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
機械支援の翻訳下書き (Japanese) 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.
“例文の下書き: 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.”
機械支援の翻訳下書き (Japanese) for "Infrastructure Approval Step": Infrastructure Approval Step is a devops workflow control that requires review before a sensitive change proceeds for cloud resources and platform wiring. It uses role checks, comments, and audit logs so teams can keep high-risk automation accountable while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Infrastructure Approval Step when a new region was added, so the team could keep high-risk automation accountable before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Cache Cold Start Budget": Cache Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for fast temporary data layer. 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.
“例文の下書き: The platform engineering team used Cache Cold Start Budget when the cache missed during peak traffic, so the team could keep first requests responsive before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Queue Isolation Boundary": Queue Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for asynchronous work buffer. 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 Queue Isolation Boundary when the queue depth increased, so the team could reduce cross-workload risk before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Memory Cache Invalidation": Memory Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for volatile runtime storage. 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 Memory Cache Invalidation when the process approached its memory limit, so the team could serve current results before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Cluster Runtime Profile": Cluster Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for group of machines acting as one platform. It uses sampling, traces, and resource metrics so teams can target optimization work while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The platform engineering team used Cluster Runtime Profile when the cluster added a node pool, so the team could target optimization work before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "TLS Path Trace": TLS Path Trace is a networking diagnostic record that shows where traffic travels and where delay or loss appears for encrypted transport setup. It uses hop data, timing, and network metadata so teams can debug connectivity issues while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The network engineering team used TLS Path Trace when a certificate neared expiration, so the team could debug connectivity issues before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) for "Container Cache Invalidation": Container Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for packaged application 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.
“例文の下書き: The platform engineering team used Container Cache Invalidation when the image started on a new node, so the team could serve current results before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Container Runtime Profile": Container Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for packaged application runtime. It uses sampling, traces, and resource metrics so teams can target optimization work while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The platform engineering team used Container Runtime Profile when the image started on a new node, so the team could target optimization work before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Memory Placement Strategy": Memory Placement Strategy is a compute scheduling rule that chooses where workloads should run for volatile runtime storage. 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 Memory Placement Strategy when the process approached its memory limit, so the team could improve reliability and efficiency before the workload scaled up.”