fluxSERVICE REGISTRY

Redirect load balancing,
simplified.

Flux is a lightweight service registry and HTTP redirect balancer — no reverse proxy, no proxy overhead.

How It Works

Three operations. One registry. Zero configuration files.

Redis-backed, TTL-based health tracking. Services expire automatically — no heartbeats, no polling.

HTTP 302 with round-robin selection. Client goes direct — no proxy overhead, no buffer.

RESTful, JSON over HTTP. Register, discover, list — three endpoints, everything you need.

Client

302

flux

Service A

Service B

Try it in 30 seconds. Start flux, register a service, discover it.

Shell

$▌ curl -X POST http://localhost:8080/register \
  -H "Content-Type: application/json" \
  -d '{"name":"my-service","address":"10.0.0.1:9000"}'

Response

$ curl http://localhost:8080/discover/my-service
302 Found
Location: http://10.0.0.1:9000

Flux is not a proxy. It tells the client where to go — and gets out of the way.

	flux	Reverse Proxy (nginx, HAProxy, Envoy)
Latency overhead	~1ms (DNS + redirect)	Proxy buffer + forward (varies)
Traffic model	Client direct to service	All traffic through proxy
Configuration	REST API, no config files	YAML/conf, reload required
Scaling	Stateless, add more flux nodes	Scale proxy pool + config sync
Best for	Service discovery + redirect	Traffic inspection, TLS termination

Use flux when you need service discovery + redirect. Use a reverse proxy when you need traffic inspection, TLS termination, or content routing.