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.
5,641 definitions
Server Reflexive Candidate Handrail is a NAT Traversal and P2P Gaming term for server reflexive candidate handrail work that shows why a multiplayer lobby, voice call, or real-time app can fail when address translation hides peers behind layers of private or shared network space. It helps people and agents name the signal, source, and safe next step without pretending an automation, campaign, DNS record, RFC, or network path did more than the evidence shows. Source context: RFC 6598 shared address space; RFC 8445 ICE; RFC 1918 private address space.
Server Reflexive Candidate Lobby Check is a NAT Traversal and P2P Gaming term for server reflexive candidate lobby check work that shows why a multiplayer lobby, voice call, or real-time app can fail when address translation hides peers behind layers of private or shared network space. It helps people and agents name the signal, source, and safe next step without pretending an automation, campaign, DNS record, RFC, or network path did more than the evidence shows. Source context: RFC 6598 shared address space; RFC 8445 ICE; RFC 1918 private address space.
Server Reflexive Candidate Mirror is a NAT Traversal and P2P Gaming term for server reflexive candidate mirror work that shows why a multiplayer lobby, voice call, or real-time app can fail when address translation hides peers behind layers of private or shared network space. It helps people and agents name the signal, source, and safe next step without pretending an automation, campaign, DNS record, RFC, or network path did more than the evidence shows. Source context: RFC 6598 shared address space; RFC 8445 ICE; RFC 1918 private address space.
Server Reflexive Candidate Proof is a NAT Traversal and P2P Gaming term for server reflexive candidate proof work that shows why a multiplayer lobby, voice call, or real-time app can fail when address translation hides peers behind layers of private or shared network space. It helps people and agents name the signal, source, and safe next step without pretending an automation, campaign, DNS record, RFC, or network path did more than the evidence shows. Source context: RFC 6598 shared address space; RFC 8445 ICE; RFC 1918 private address space.
Serverless Autoscaling Policy is a compute control loop that changes capacity based on demand signals for event-driven function execution. It uses metrics, thresholds, and cooldowns so teams can match resources to load while keeping evidence, reliability, and public-safe operational boundaries clear.
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.
Serverless Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for event-driven function execution. It uses keys, tags, timestamps, and purge events so teams can serve current results while keeping evidence, reliability, and public-safe operational boundaries clear.
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.
Serverless Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for event-driven function execution. 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.
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.