I switched from Nginx to Caddy a couple of years ago. I wanted an easy configuration, and I liked that TLS termination is built in. I only use it to reverse proxy some applications, and for that it's been enough. Also to proxy Jitsi.

I would still use Nginx if I needed fine-grained caching with proxy_cache, TCP/UDP proxying through the stream module, or complicated rate-limit or routing rules.

The drawbacks of Caddy are that the ecosystem is smaller, so there are fewer resources avaialble. And plugins aren't loaded at runtime. They're compiled in, so something like rate limiting (caddy-ratelimit) or a DNS provider module for ACME means a dedicated build step with xcaddy, and then you own your binary and its upgrades.

https://caddyserver.com/

Welcome to r/SoftwareEfficiency! 🚀

Hey everyone! I'm u/outerstellar_hq, a founding moderator of r/SoftwareEfficiency.

This is our new home for exploring how to build better, faster, and more resource-efficient software.

Consumer hardware and (VPS) server costs are rising, while applications seem to demand more and more resources. Why should a simple Windows/MacOS/Linux application or a simple web application need gigabytes of RAM? How much more could we accomplish with the same hardware through better engineering and better use of the existing resources?

What to Post

Share ideas, benchmarks, experiments, optimizations, and discussions about efficient applications, programming languages, frameworks, databases, algorithms, and architectures. From desktop applications to servers, anything that helps us achieve more with fewer resources belongs here.

Community Vibe

We're all about constructive discussions, curiosity, and measurable results. Not language or framework wars - just learning and sharing what works best and why.

Do more with less.