Go · reverse proxy · distributed systems
Traffic control for services that remember.
A multi-core Go load balancer for stateful and stateless backends. It routes requests, moves owned state through a fenced handoff, and sheds excess work before a slow service becomes a system-wide problem.
- Gosingle process
- 7routing policies
- Redisshared coordination
Routing is the beginning.
Correctness is the feature.
System shape
One edge. Several ways to stay correct.
Route policy is selected by the longest matching prefix. Health, ownership, retries, cache behavior, and admission remain separate decisions with explicit boundaries.
Safe state movement
A handoff is a protocol, not a redirect.
Changing a route is easy. Moving live state without losing ownership takes a sequence with durable checkpoints.
Engineering decisions
Make failure behavior visible.
The system favors bounded work and explicit recovery over hidden retries or automatic reassignment.
Verification
Test the failure path, too.
Acceptance work covers routing behavior, Redis-backed coordination, bounded queues, race conditions, recovery, and the dashboard’s live path.
View continuous integration- Seven routing modes
Verified through a live fixture cluster.
- Concurrency safety
Race detector plus targeted admission and handoff tests.
- Failure recovery
Redis outage, cancellation, retry, and owner recovery paths.
- Reproducible overload
Latency percentiles, throughput, and bounded queue checks.
Explore the project
See how the pieces behave together.
Browse the running dashboard, run fixture traffic, or trace the implementation in the repository.