4 ms·
If anything, putting a good reverse proxy in front of your server tends to improve performance, by managing your request queue for you and smoothing out bursts.
by kqr 6y ago
If anything, putting a good reverse proxy in front of your server tends to improve performance, by managing your request queue for you and smoothing out bursts. Queue management is hard and not what you (probably) want to spend your time on.
- yjftsjthsd-h 6y agoI could see it going either way: Putting nginx in front adds another hop for traffic, but indeed gives you all of nginx's performance optimizations. But either way you're obscuring the performance of your code.
- kqr 6y agoWell, sure, that's technically correct. The performance of your code is not what's ultimately interesting, though. The performance of the system you have designed is. And that might very sensibly include nginx! In fact, if you design your system with nginx as the ingress point, you are likely to make tradeoffs that mean your code performs worse in isolation, in order to get optimum performance out of the entire system!