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 "Serverless Cold Start Budget": Serverless Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for event-driven function execution. 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 Serverless Cold Start Budget when the function received a traffic burst, so the team could keep first requests responsive before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Cache Runtime Profile": Cache Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for fast temporary data layer. 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 Cache Runtime Profile when the cache missed during peak traffic, so the team could target optimization work before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Observability Infra Plan": Observability Infra Plan is a devops change preview that shows expected infrastructure changes before apply for logs, metrics, traces, and events. It uses resource graphs, policy checks, and cost notes so teams can review platform changes safely while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Observability Infra Plan when latency increased after deploy, so the team could review platform changes safely before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Release Runbook Check": Release Runbook Check is a devops operational test that confirms that documented procedures still work for versioned delivery of code or content. 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 Release Runbook Check when the release notes were generated, so the team could keep response playbooks current before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Storage Workload Priority": Storage Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for persistent data and object access. 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 Storage Workload Priority when the workload read a large dataset, so the team could protect critical paths before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "BGP Anycast Endpoint": BGP Anycast Endpoint is a networking routing pattern that advertises one address from multiple locations for interdomain routing. It uses regional announcements, health checks, and traffic steering so teams can serve users from nearby healthy sites while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The network engineering team used BGP Anycast Endpoint when a route advertisement changed, so the team could serve users from nearby healthy sites before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) for "Secret Infra Plan": Secret Infra Plan is a devops change preview that shows expected infrastructure changes before apply for credential and sensitive configuration. It uses resource graphs, policy checks, and cost notes so teams can review platform changes safely while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Secret Infra Plan when a token rotated, so the team could review platform changes safely before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "CPU Runtime Profile": CPU Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for general-purpose processor scheduling. 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 CPU Runtime Profile when the service hit a compute ceiling, so the team could target optimization work before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Infrastructure Secret Rotation": Infrastructure Secret Rotation is a devops credential workflow that replaces sensitive keys without service interruption for cloud resources and platform wiring. It uses dual credentials, rollout steps, and revocation so teams can reduce credential exposure while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Infrastructure Secret Rotation when a new region was added, so the team could reduce credential exposure before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Runbook Artifact Signature": Runbook Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for documented operational procedure. It uses cryptographic signatures, provenance, and verification so teams can trust deployed packages while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Runbook Artifact Signature when a responder needed the recovery steps, so the team could trust deployed packages before the deployment window opened.”