Init guide environment...
Requests distributed in fixed circular order. Perfect for identical backend servers.
Routes to the server with fewest active requests. Ideal for long-lived connections.
Assigns more traffic to powerful servers. Distributes by capacity weight index.
Client IP determines server mapping. Ensures same user visits same server (Sticky Session).
Routes to server with lowest latency and fewest connections. Performance-aware.
Hash ring algorithm. Only affected keys remapped when servers change. Minimal cache invalidation.
Visualize how requests are routed in real-time
Transport layer vs Application layer routing
| Algorithm | Complexity | Session Affinity | Load Aware | Best For |
|---|---|---|---|---|
| Round Robin | ✗ No | ✗ No | Stateless apps, equal servers | |
| Least Connections | ✗ No | ✓ Yes | Long-lived connections, WebSockets | |
| Weighted Round Robin | ✗ No | ✓ Yes | Mixed hardware, different specs | |
| IP Hash | ✓ Yes | ✗ No | Stateful apps, session caching | |
| Least Response Time | ✗ No | ✓ Yes | Performance-critical, geo-distributed | |
| Consistent Hashing | ✓ Yes | ✗ No | Distributed caches, CDN routing |