cosmo VS Caddy

At the very beginning, I was a solo founder and put my project WunderGraph (https://github.com/wundergraph/cosmo) on GitHub.

After a while, a CTO contacted me and asked if I could "support" his team and add some features that he wanted. After a month of sweating, we agreed that they'd pay me a monthly support subscription of $2k.

I learned a lot from the use cases, improved the software, and got some more users, which ultimately was enough of a story for VCs to raise a $3M seed round, which I think is quite cool as a first-time founder from Germany with zero connections, no YC friends, etc...

I quickly realized that I could not pull this off alone, so I teamed up with 3 fantastic Co-Founders who are responsible for the business side, marketing, sales, and engineering.

Fast forward two years and we're growing our customer base at a great pace and are slowly looking towards a Series A. I can tell though that the way from our first customer to where we are now was extremely tough. We're in enterprise sales, we had to switch our strategy at some point. Lots of learning, lots of pain.

In retrospect, I wouldn't say that the first customer is the hardest. Building a repeatable sales motion is much harder. Building a product, marketing, and sales process that all aligns well for repeatable sales is a lot of work.

Whoever tries this, good luck and please connect if you need help as a founder or want some advice. I love to help others to start their own business. It's hard, but it's also a life that I don't want to miss.

👉 Cosmo on GitHub: The code

By leveraging the astjson package, we were able to speed up our GraphQL API Gateway (Cosmo Router) while reducing the memory footprint. At the macro level, we were able to increase requests per second by 23% and reduced p99 latency by 44% over the previous version of Cosmo Router. At the micro level, we reduced the memory usage of a benchmark by 60%.

To learn more, go check out their docs here. Also, the WunderGraph Discord can be found here, if you have questions or issues you want to discuss.

For the future, we're working hard on adding compatibility with Federation 2.x features, If you find any bugs or have feature requests, please open an issue on GitHub.

If you want to learn more about Cosmo, check out the documentation.

No, look at the associated unit test: https://github.com/caddyserver/caddy/blob/c6eb186064091c79f4...

If that test fails we could serve PHP source code instead of having it be evaluated, a major security flaw.

However, it's very unlikely that .NET developers will directly expose their Kestrel-based web apps to the internet. Typically, we use other popular web servers like Nginx, Traefik, and Caddy to act as a reverse-proxy in front of Kestrel for various reasons:

I think that recompiling with upgraded Go will not solve the issue. It seems Caddy imports `golang.org/x/net/http2` and pins it to v0.22.0 which is vulnerable: https://github.com/caddyserver/caddy/issues/6219#issuecommen....

Caddy [1] is a single binary. It is not minimal, but the size difference is barely noticeable.

serve also comes to mind. If you have node installed, `npx serve .` does exactly that.

There are a few go projects that fit your description, none of them very popular, probably because they end up being a 20-line wrapper around http frameworks just like this one.

[1] https://caddyserver.com/

Each app’s front end is built with Qwik and uses Tailwind for styling. The server-side is powered by Qwik City (Qwik’s official meta-framework) and runs on Node.js hosted on a shared Linode VPS. The apps also use PM2 for process management and Caddy as a reverse proxy and SSL provisioner. The data is stored in a PostgreSQL database that also runs on a shared Linode VPS. The apps interact with the database using Drizzle, an Object-Relational Mapper (ORM) for JavaScript. The entire infrastructure for both apps is managed with Terraform using the Terraform Linode provider, which was new to me, but made provisioning and destroying infrastructure really fast and easy (once I learned how it all worked).

So I dug a little deeper and came across this gem: Caddy. Caddy is this fantastic, extensible, cross-platform, open-source web server that's written in Go. The best part? It comes with automatic HTTPS. It basically condenses all the work our scripts and manual maintenance were doing into just 4-5 lines of config. So, stick around and I'll walk you through how to set up an automatic SSL solution with Caddy, Docker and a Node.js server.

Let's use Caddy which can act as reverse-proxy with automatic HTTPS coverage.

Even if it may be simple, it doesn't handle edge cases such as https://github.com/caddyserver/caddy/issues/1632

I personally would make the trade off of taking on more complexity so that I can have extra compatibility.

One of the most heavily used Russian software projects on the internet https://www.nginx.com/blog/do-svidaniya-igor-thank-you-for-n... but it's only marginally more modern than Apache httpd.

In light of recently announced nginx memory-safety vulnerabilities I'd suggest migrating to Caddy https://caddyserver.com/