4 ms·
At what point does one use Caddy over writing a server with few lines in Go/Node. A bit confused on the use case of Caddy.
by nikivi 6y ago
At what point does one use Caddy over writing a server with few lines in Go/Node. A bit confused on the use case of Caddy.
- hairyhenderson 6y agoUse Caddy wherever you'd otherwise use Apache HTTPD, nginx, IIS, traefik, Kong, etc...
- molszanski 6y agoWhy traefik? They both seem to be amazing modern web servers
- dubcanada 6y agoIt's comparable to Nginx and Apache, not a Go/Node http/https server.
- tyingq 6y agoI imagine it's quite a lot more than a few lines of code to correctly handle HEAD requests, ssl/tls, etags, expires headers, and so on.
- cthalupa 6y agoI see Caddy as your general use case production web server prior to hitting large scaling needs. I've never gotten it to perform as leanly or scale as well as nginx, but most people will probably not need the headroom nginx provides vs. caddy. Caddy is significantly easier to manage and get running to a "good enough" stage for people that aren't familiar with nginx and apache, even for most medium sized production deployments. But, if you've got a team that's comfortable with nginx or apache, and doesn't find themselves spending an undue amount of time fiddling around with managing them, I don't personally believe there's any reason to switch from them to caddy.
- QUFB 6y agoCaddy's TLS features are available in CertMagic (https://github.com/caddyserver/certmagic https://github.com/caddyserver/certmagic) for your daily Golang web app development. Highly recommended!