Cloud Native Reverse Proxy

The Cloud Native Reverse Proxy is a dynamic multi-source reverse proxy written in Go and inspired by Traefik. Application backends declare themselves and the proxy automatically discovers relevant services, builds routing rules, and load-balances live HTTP traffic to them without configuration changes.

Features

• Automatic service discovery with live routing updates as services start/restart/stop, requiring no proxy restart or configuration changes
• Self-healing route registry that continuously reconciles against running backends, staying accurate through network partitions
• Load-balancing over multiple replicas with distribution of incoming requests across all backends associated with the target host
• Fault-tolerant routing with automatic reconnection on backend failures while ensuring uninterrupted delivery of existing traffic through outages
• Source-scoped route ownership where each provider manages only the routes it discovers, reconciling independently without overwriting one another
• Backpressure-aware event ingestion through bounded internal buffers with a defined overflow policy, absorbing large bursts of engine API events without exhausting memory or stalling the proxy

The Cloud Native Reverse Proxy currently supports deployments on Docker and Kubernetes backends, with ECS and etcd on the roadmap in the near future.

Architecture

Requirements

• just to run development/test workflows and deploy docker/kubernetes backends locally
• Docker for the Docker provider and local backends
• minikube and kubectl for the Kubernetes provider and local backends

Run Locally

• just --list: View all helper commands
• just clean: Tear development environment down

Docker Backends

• just docker-dev-up n: Create n (default 3) sample hashicorp/http-echo backends with pre-configured labels, build + run the proxy, and output logs
• just docker-test-curl: Send a HTTP request to localhost with the Host: test.localhost header, which will get forwarded to the intended container backend
• just docker-test-down-one n and just docker-test-restart n: Tear down or restart the nth backend container to see the registry update in real time

Kubernetes Backends

• just k8s-dev-up: Create pre-configured sample backend deployments/services/ingresses and deploy the proxy within minikube
• just k8s-proxy-forward: Use minikube tunnel to port forward the sample backends to localhost
• just k8s-test-curl: Send a HTTP request to localhost with the Host: test.localhost header, which will get forwarded to the intended kubernetes service