3 ms·
Yes, I think is better to put nginx in front to handle this and sooner or later you will need some kind of reverse proxy as soon as your application grows. The
by jfroma 12y ago
Yes, I think is better to put nginx in front to handle this and sooner or later you will need some kind of reverse proxy as soon as your application grows. The reasons might be load balancing or just to map components of your app like "app.com" and "app.com/api" being different applications.
One big difference to note is that nginx link to the local openssl while node binaries embeds an openssl. If there is a bug in openssl I can apt-get update/upgrade and I get the patch very early.
Personally I think nginx is awesome. They are going to support JavaScript soon, but I have done things with LUA and is great too.
- eugeneionesco 12y ago>Personally I think nginx is awesome. They are going to support JavaScript soon Whaaaaaaat?
- jfroma 12y agoCan't find a better source but it was announced few months ago: http://www.infoworld.com/article/2838008/javascript/nginx-has-big-plans-for-javascript.html http://www.infoworld.com/article/2838008/javascript/nginx-ha...
- jared314 12y ago> They are going to support JavaScript soon Whoa. Slow down. They have only confirmed replacing their custom configuration language with JavaScript and hinted at an official JavaScript module [1], as opposed to the existing third-party module [2]. Bundling a Node.js-like JavaScript api layer with their official module would be a logical next step, because nginx is an event loop anyway. But, I highly doubt JavaScript will be anywhere near the Nginx core. [1] http://www.infoworld.com/article/2838008/javascript/nginx-has-big-plans-for-javascript.html http://www.infoworld.com/article/2838008/javascript/nginx-ha... [2] https://code.google.com/p/ngxv8/ https://code.google.com/p/ngxv8/
- jfroma 12y agoThanks for the clarification, that's what I though but my comment was quite vague