maglev

Design and audit Maglev-style load balancing configurations for VIP management, backend pools, health checks, and ECMP routing.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/CYBERSTALKER07/ATOMOS --skill maglev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maglev
Source: https://github.com/CYBERSTALKER07/ATOMOS/tree/main/.agents/skills/maglev
Command: npx skills add https://github.com/CYBERSTALKER07/ATOMOS --skill maglev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Maglev-style load balancing designs address high-throughput, low-latency traffic routing across large backend pools while preserving per-connection consistency and rapid failover.

Core Features & Use Cases

  • Consistent hashing-based backend selection that minimizes disruption when backends are added or removed.
  • VIP-to-backend routing with health-check integration and ECMP-friendly distribution for scalable deployments.
  • Observability and operational guidance for testing, rollout, and security considerations in hyperscale environments.

Quick Start

Deploy a Maglev-like forwarder and verify that VIPs map to healthy backends while maintaining per-connection affinity during rolling updates.

Frequently Asked Questions about maglev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does consistent hashing work in Maglev load balancing?

Maglev consistent hashing maps VIPs to backend pools using a lookup table that minimizes disruption when backends are added or removed, preserving per-connection affinity during rolling updates.

How do I configure VIP routing with health checks for hyperscale load balancing?

Configure VIP-to-backend routing by integrating health checks with ECMP-friendly distribution, ensuring traffic routes only to healthy backends while maintaining deterministic Maglev hashing across the pool.

What's the best way to audit a Maglev-style load balancing configuration?

Audit Maglev configurations by reviewing per-connection tracking, atomic config updates, ECMP routing distribution, and health-check integration to ensure deterministic hashing and rapid failover in hyperscale deployments.

Does Maglev consistent hashing support per-connection affinity during backend pool changes?

Yes, Maglev consistent hashing preserves per-connection affinity by using a lookup table that remaps minimal entries when backends change, keeping active connections stable during rolling updates and failover.

When should I use Maglev-style load balancing instead of other consistent hashing approaches?

Use Maglev-style load balancing for hyperscale deployments requiring high-throughput, low-latency traffic routing with ECMP-friendly distribution, deterministic hashing, and rapid failover across large backend pools.