*nginx* is not a bad choice, but would instead recommend *node-http-proxy* for m... | Hacker News

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

wamatt on Oct 1, 2012 | parent | context | favorite | on: RailwayJS

nginx is not a bad choice, but would instead recommend node-http-proxy for most projects (including production).

It's fast, easy to setup (npm install), and relatively hardened, while still keeping everything JS.

As for static assets, those should probably be served from a CDN anyway, if one is concerned with performance.

louischatriot on Oct 1, 2012 [–]

I agree about the CDN, even though for us performance is not so critical we need to use a CDN (yet). I didn't know node-http-proxy but it sounds interesting I'll check it out.

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