▲ 6 ▼ Ask: Is anyone using caddy in production yet?
I'd like to try out Caddy for production sites, but wondered if anyone has any experience with it.
Register to comment or vote on this story
I'd like to try out Caddy for production sites, but wondered if anyone has any experience with it.
Hi Rijwan, did you attempt to add a comment here and had a problem posting?
You can use it in production. I am. Gopher Academy is. I know of a few companies that are.
Thanks, that's good to know, I'm considering replacing nginx as a proxy in front of go apps with caddy.
Done! This site is now served by Caddy on a $5 DO instance.
Using a combination of Flask and Nginx at the moment. Exploring the Go and Caddy for that. I use Go and Python both. But Go is performing better at the moment
The main advantage I've seen in using Go (comparing to Ruby, rather than Python), is a vast decrease in memory usage. This site is running on a $5 DO instance at present, and seems to handle load of up to 100 concurrent users on that fine (when load testing), which is pretty good for such a tiny instance. The caddy process is taking up roughly 4%, docker 5% and the go backend around 2%, so memory profiles are pretty minimal, and performance is pretty good. I'd definitely recommend it replacing nginx (which I was using previously) - the config files are v. similar slightly better if anything, and the proxy stuff works in a very similar way, so it's a smooth transition.
Caddy is based on the net/http code from the golang std lib so it's pretty solid and likewise doesn't take up much memory. Nice that it gets things like http2 for free as well as the great work on tls. I haven't been using it for very long, but am happy with it so far. Will report back after I've tried it on a few other sites, and used it for longer.
Just as an update, this site was served with caddy server for about a year, without issues, primarily for the letsencrypt integration (it was one of the first to have it). I've now switched to serving directly with the latest version of Go in a single process, and will soon be enabling autocert support. As @matt says above though, it has been used on some large-ish sites for some time now, so anyone wondering if it is production ready, the answer at this point is definitely yes.