News for hackers. Stuff that matters.
Re:Monzo’s Response to Cloudbleed by atmosx on Friday February 24, 2017 @11:25AM (#13725024)
Caddy[1] is written in Go and has a nicer, simpler syntax. I'm sure NGINX has many more features though.

[1] https://github.com/mholt/caddy

Re:Monzo’s Response to Cloudbleed by rnhmjoj on Friday February 24, 2017 @01:05PM (#13725980)
Ironically as I was considering Caddy as an NGINX alternative I found about a security issue that is very reminiscent of what happened at cloudflare:

https://github.com/mholt/caddy/issues/1204#issuecomment-2781...

Re:Monzo’s Response to Cloudbleed by fortytw2 on Friday February 24, 2017 @11:40AM (#13725185)
Caddy has less than half the performance of Nginx - not really a viable replacement at any sort of scale. https://hackernoon.com/caddy-a-modern-web-server-vs-nginx-e9...
Re:Monzo’s Response to Cloudbleed by Filligree on Friday February 24, 2017 @12:02PM (#13725425)
Depends on what you're doing. If it's fronting an expensive web-app, then the couple hundred CPU-microseconds needed to proxy a request isn't going to be noticeable...

Caddy can serve 5,000 requests per second per core. I would flip your statement on its head, and say that a minority of people need anything close to that. The few companies that do, can probably afford to keep on top of CVEs for their frontends as well.

Re:Monzo’s Response to Cloudbleed by shawabawa3 on Friday February 24, 2017 @12:34PM (#13725690)
That's misleading at best.

Empty request benchmarks are indicative of nothing in the real world.

For any reasonable workload, even serving static sites of a few kilobytes they will be effectively the same.

Caddy's sane default settings (enforcing SSL, and with correct settings to get an A+ on SSL labs) make it the right choice for a lot of deployments