3 ms·

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, unl

by dsl 8y ago

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."

deleted 8y ago
[deleted]
brightball 8y ago
How’s Apache doing these days? Haven’t looked in a while
- skoskie 8y ago
  Nowhere near as fast with concurrent connections.
  - jimjag 8y ago
    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.
keypusher 8y ago
Put a load balancer between your reverse proxy and your backends. Problem solved.
- corebit 8y ago
  What do you think nginx was being used for?