and Ĭurrently, my biggest gripe is that Nginx kills itself when it cannot resolve an upstream host, for example, while Docker containers are still starting, their health checks haven't passed and therefore their DNS records also haven't been created. For example, both of these seem more passable to me when compared to Apache2.
And my containers can have all of the necessary config in a single file vs the unnecessary boilerplate fragmentation that httpd forces upon me. I no longer even need rewrite rules to get websockets working properly, which is nice. Nginx - recently migrated my ingress to it at work, seems pretty okay so far, the configuration format seems to make a bit more sense and probably lies somewhere between Apache and Caddy as far as its ease of use and pleasantness goes. The further down you scroll, the less user friendly it becomes: 95% of the cases, though that might change with frameworks like Vert.X or such. The performance is still passable, no matter what anyone says, my applications still have been the bottleneck in approx. That said, i have certain grievances with most of the web servers out there.Īpache2/httpd - actually decently usable even nowadays, but if the fragmentation of service names (httpd vs apache2, with additional scripts like a2enmod) between different distros doesn't hurt it, then the configuration format and how it does reverse proxying and path rewriting most certainly will.
That said, i can't help but to feel that v1 was easier and in some ways nicer to use than v2, even though it's abandoned at this point. In my eyes, Caddy is a lovely web server that works pretty well as ingress for container clusters (e.g.
0 kommentar(er)
