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
기계 지원 번역 초안 (Korean) for "Cluster Checkpoint Restore": Cluster Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for group of machines acting as one platform. 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 Cluster Checkpoint Restore when the cluster added a node pool, so the team could recover long-running work before the workload scaled up.”
기계 지원 번역 초안 (Korean) for "CPU Workload Priority": CPU Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for general-purpose processor scheduling. 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.
“예문 초안: The platform engineering team used CPU Workload Priority when the service hit a compute ceiling, so the team could protect critical paths before the workload scaled up.”
기계 지원 번역 초안 (Korean) for "Infrastructure Runbook Check": Infrastructure Runbook Check is a devops operational test that confirms that documented procedures still work for cloud resources and platform wiring. It uses dry runs, screenshots, and command validation so teams can keep response playbooks current while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The DevOps team used Infrastructure Runbook Check when a new region was added, so the team could keep response playbooks current before the deployment window opened.”
기계 지원 번역 초안 (Korean) for "Serverless Capacity Forecast": Serverless Capacity Forecast is a compute planning model that estimates future resource needs for event-driven function execution. It uses traffic history, growth assumptions, and utilization trends so teams can avoid surprise shortages while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The platform engineering team used Serverless Capacity Forecast when the function received a traffic burst, so the team could avoid surprise shortages before the workload scaled up.”
기계 지원 번역 초안 (Korean) for "Scheduler Autoscaling Policy": Scheduler Autoscaling Policy is a compute control loop that changes capacity based on demand signals for placement of work onto resources. 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 Scheduler Autoscaling Policy when the cluster needed to place a job, so the team could match resources to load before the workload scaled up.”
기계 지원 번역 초안 (Korean) for "CPU Checkpoint Restore": CPU Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for general-purpose processor scheduling. 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 CPU Checkpoint Restore when the service hit a compute ceiling, so the team could recover long-running work before the workload scaled up.”
기계 지원 번역 초안 (Korean) for "Edge Workload Priority": Edge Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for globally distributed runtime. 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.
“예문 초안: The platform engineering team used Edge Workload Priority when the request arrived near a user, so the team could protect critical paths before the workload scaled up.”
기계 지원 번역 초안 (Korean) for "Container Cold Start Budget": Container Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for packaged application runtime. 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 Container Cold Start Budget when the image started on a new node, so the team could keep first requests responsive before the workload scaled up.”
기계 지원 번역 초안 (Korean) for "DNS Traffic Shaper": DNS Traffic Shaper is a networking control mechanism that limits or prioritizes flows across links for name resolution and delegation. It uses queues, rate limits, and quality-of-service rules so teams can protect important traffic while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The network engineering team used DNS Traffic Shaper when a resolver returned stale data, so the team could protect important traffic before traffic crossed a service boundary.”
기계 지원 번역 초안 (Korean) for "Edge Capacity Forecast": Edge Capacity Forecast is a compute planning model that estimates future resource needs for globally distributed runtime. It uses traffic history, growth assumptions, and utilization trends so teams can avoid surprise shortages while keeping evidence, reliability, and public-safe operational boundaries clear.
“예문 초안: The platform engineering team used Edge Capacity Forecast when the request arrived near a user, so the team could avoid surprise shortages before the workload scaled up.”