go-proxy

A simple proxy implementation for the mondern day

This project aims to produce a programmable proxy to facilitate Ambassador pattern. Find out more about Ambassador in micro service deployment

go-proxy strives to achieve the following goals

• To be not complicated
• Code is the docuementation
• Exist as a standalone program and a library for proxy
• Interface with discovery backend
• Be as lean as possible

Import go-proxy as library

go get github.com/jeffjen/go-proxy/proxy

Running go-proxy as a standalone program

• Running with static candidates:

  go-proxy --src :16379 --dst 10.0.3.144:6379
  

• Running with discovery backend:

  go-proxy --dsc http://etcd0:2379 --dsc http://etcd1:2379 \
      --src :16379 \
      --srv /srv/redis/debug
  

Behavior

The proxy module does not attempt to perform reconnection to remote endpoint. The rule is fail fast retry.

When connected with a discovery backend, nodes are registered under a key e.g. /srv/redis/debug, with the last segment being the actual netloc of the node in that service i.e. /srv/redis/debug/10.0.1.134:6379, /srv/redis/debug/10.0.2.122:6379.

When members in the /srv/redis/debug service changes e.g. leaving, joining, the proxy will reject established connections (if not already broken from the view point of connected client).