Go Infrastructure Project

EdgeBalancer

A live traffic router that demonstrates the systems work recruiters look for: health-aware routing, bounded failure handling, protected control planes, and operational metrics running on AWS ECS/Fargate.

Open Control Plane View Metrics Architecture
Health Checks Round Robin Least Connections Circuit Breakers Rate Limiting Metrics Dashboard

Portfolio Signal

Infrastructure Depth In One Running System

HC

Health Checks

Active probes remove failing backends from rotation and restore them only after recovery thresholds are met.

RR

Round Robin

Fair request distribution across healthy nodes for homogeneous backend pools.

LC

Least Connections

Routes new traffic toward less-busy backends when request durations are uneven.

CB

Circuit Breakers

Stops repeatedly failing upstreams from absorbing traffic during an outage window.

RL

Rate Limiting

Token-bucket protection reduces overload risk before traffic reaches upstream services.

MD

Metrics Dashboard

Live counters expose request volume, retries, failovers, upstream errors, and backend selection.

Live Control Plane

Routing Strategy And Backend Health

Vercel serves this static page while AWS ECS can scale to zero. Backend controls wake ECS, then read from /admin/backends, /admin/strategy, and /admin/cost.

Current Strategy Loading...
Proxy Endpoint /proxy/
Estimated Cost loading...

Metrics Dashboard

Reliability And Traffic Counters

Total Requests 0
In Flight 0
Retries 0
Failovers 0
Upstream Errors 0
Circuit Opens 0

Status Classes

Backend Selection

Route Method Samples Avg Latency
Loading metrics...

Request Path

How EdgeBalancer Handles Traffic

  1. Vercel serves the static frontend from the edge for the recruiter-facing dashboard.
  2. Backend paths first hit a Lambda wake gateway that can scale ECS services from 0 to 1.
  3. API paths such as /admin/*, /ai/*, /metrics, and /proxy/* are then proxied to the AWS CloudFront, ALB, and ECS/Fargate backend.
  4. Rate limiting and request tracing run inside the Go load balancer before proxy forwarding.
  5. EdgeBalancer chooses a healthy backend with the active strategy.
  6. Retries and circuit breakers isolate upstream failures from client traffic.
  7. Metrics and structured logs record request, backend, latency, and failover behavior.

Routing Algorithms

Strategy Trade-offs

Round Robin

Best when backend capacity and response time are similar.

Least Connections

Best when some requests hold connections longer than others.

Weighted Routing

Best when stronger nodes should carry a larger traffic share.

Consistent Hashing

Best when cache locality or request affinity matters.

AI Copilot

Runtime-Aware Architecture Guidance

AI Provider loading...
AI response will appear here.