Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

NGINX was already paywalling bug fixes once they launched Pro.

proxy_pass for example will only resolve a hostname at the time the configuration is parsed, unless you use a convoluted variable hack. This was a serious issue requiring you to restart your fleet if a backend server changed IPs. The bug fix for this was implemented only in Pro and sold as "DNS for Service Discovery."



Put a load balancer between your reverse proxy and your backends. Problem solved.


What do you think nginx was being used for?


How’s Apache doing these days? Haven’t looked in a while


Nowhere near as fast with concurrent connections.


That is simply untrue. Apache 2.4.x w/ the Event MPM is just as fast and actually has lower latency. That FUD has long, long since been disproved.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: