I've used a reverse proxy, written in Go in production. It did perform as
good and even slightly better than nginx for our use case. It was regularly
keeping 10GBps LAN cards full to the brim without much sweat. Our use case
was serving and caching constantly changing library of huge media files
Strangely we just tried deploying a really simple one but with large-ish
POST payloads. For some reason the number of requests/s would never match
what would hit the nginx servers directly without the Go proxy.
wrk & ab profiles were able to cope but as soon as any real world traffic
hit the
