Nginx to Be Acquired by F5 Networks

Re:Nginx to Be Acquired by F5 Networks by dsl on Monday March 11, 2019 @07:47PM (#19364040)

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

[ Parent | on HN ]

Re:Nginx to Be Acquired by F5 Networks by keypusher on Tuesday March 12, 2019 @04:47AM (#19366370)

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

[ Parent | on HN ]

Re:Nginx to Be Acquired by F5 Networks by corebit on Tuesday March 12, 2019 @08:56AM (#19367624)

What do you think nginx was being used for?

[ Parent | on HN ]

Re:Nginx to Be Acquired by F5 Networks by brightball on Monday March 11, 2019 @11:13PM (#19365065)

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

[ Parent | on HN ]

Re:Nginx to Be Acquired by F5 Networks by skoskie on Monday March 11, 2019 @11:57PM (#19365302)

Nowhere near as fast with concurrent connections.

[ Parent | on HN ]

Re:Nginx to Be Acquired by F5 Networks by jimjag on Tuesday March 12, 2019 @11:18AM (#19368969)

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.

[ Parent | on HN ]