I've never noticed any performance issues, I think I saw a benchmark where it said caddy can handle 2000req/s, which is at least an order of magnitude or 2 faster than any upstream service I've used it in front of.
Those are application level numbers (e.g. with logic and all).
Caddy should be able to handle an order of magnitude more req/s than that easily.
It was slightly slower than nginx, but not enough to impact typical applications
I'm sure HN would love a more in-depth comment where you say how you're accomplishing things today and what you expect out of general purpose reverse proxies, etc.
https://www.techempower.com/benchmarks/#section=data-r12&hw=...
This is on Dell R720xd dual-Xeon E5 v2 + 10 GbE. Now if I chose technology that cuts this performance 200x times I am wasting resources.
I like to idea of Caddy but before we can consider using it in production I need to make sure it can keep up with the performance requirement we got.
But seriously, for all "hobby" projects I've started recently, and even some production services now, I go straight to caddy.
My config consists of a 1 line global config file:
And 90% of the individual services have this config: Compared to nginx it's just so much simpler and so far I haven't found myself missing a single feature. (In fact, caddy has active health checks, which nginx only supports for its extortionate enterprise fee)