4 ms·

I've been working with nginx quite a bit recently for use as a reverse proxy in a containerized environment and have become quite disenfranchised with it. For

by Rapzid 11y ago

I've been working with nginx quite a bit recently for use as a reverse proxy in a containerized environment and have become quite disenfranchised with it. For some reason it's the most popular reverse proxy for this sort of stuff, however it's not particularly well suited for it. We have this issue. We also have the lack of active upstream checks and any sort of upstream status reports. Both are hidden behind the nginx Plus paywall which is absurdly expensive in a micro-architecture world. There are various patches, Patches!?, you can apply but the documentation isn't fantastic and this is an extra bit of hassle we don't really deserve.. I think the open internet deserves a better reverse proxy TBH.

elithrar 11y ago
Have you looked into HAProxy? Health checks, SSL termination and a reasonable configuration DSL: https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts https://www.digitalocean.com/community/tutorials/an-introduc...
- Rapzid 11y ago
  I am acutely aware of HAProxy however the rest of the team is, no surprise I'm sure, familiar with nginx. Likely I'll end up doing the usual nginx->haproxy->backend chain again. HAPROXY appears to have an enterprise now(it may have had forever I just have not noticed) but it appears to be much more focused on value-add support and stack validation than hiding simple-to-implement stuff behind a paywall and open-core. This is more of a frustration with nginx which could be so much more for us if: * They were not purposely holding back features so they can be pay-walled * Re-compiling were not necessary to add functionality * More cohesive modification ecosystem I know I said "reverse proxy" which HAProxy is cleary the more superior, but I didn't mean to limit my statement to reverse proxies. nginx does have a lot of other functionality people rely on..
  - Tenzer 11y ago
    Dynamic modules are on the road map, according to this article: http://www.infoworld.com/article/2951849/web-services/nginx-to-hop-on-http-2-train.html http://www.infoworld.com/article/2951849/web-services/nginx-....

by Rapzid 11y ago

elithrar 11y ago

Have you looked into HAProxy? Health checks, SSL termination and a reasonable configuration DSL: https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts https://www.digitalocean.com/community/tutorials/an-introduc...

Rapzid 11y ago
I am acutely aware of HAProxy however the rest of the team is, no surprise I'm sure, familiar with nginx. Likely I'll end up doing the usual nginx->haproxy->backend chain again. HAPROXY appears to have an enterprise now(it may have had forever I just have not noticed) but it appears to be much more focused on value-add support and stack validation than hiding simple-to-implement stuff behind a paywall and open-core. This is more of a frustration with nginx which could be so much more for us if: * They were not purposely holding back features so they can be pay-walled * Re-compiling were not necessary to add functionality * More cohesive modification ecosystem I know I said "reverse proxy" which HAProxy is cleary the more superior, but I didn't mean to limit my statement to reverse proxies. nginx does have a lot of other functionality people rely on..
- Tenzer 11y ago
  Dynamic modules are on the road map, according to this article: http://www.infoworld.com/article/2951849/web-services/nginx-to-hop-on-http-2-train.html http://www.infoworld.com/article/2951849/web-services/nginx-....