On Tue, Feb 14, 2012 at 8:49 AM, billywhizz <[email protected]> wrote:
> Matt - there's no need to be so rude, especially to one of the best > guys in the community. > I didn't mean "benchmarks or GTFO" in any rude way - it's just that people need to understand that Node will never be the high performance static file server that nginx is. And trying to get there seems pretty futile to me - the web is GREAT at small pluggable components - so use it like that. Stick nginx up front, haproxy in front of that if you need it, and node in the backend doing your dynamic content. This design has HUGE advantages over just using Node for everything, and it's simple to manage and run. > getting close to nginx performance is > definitely achievable > Like I said, let's see some benchmarks then. I just really doubt you'll get all that close in any sane flexible manner supporting all the correct headers (eTags, If-Modified-Since, etc). There's value in having both node and nginx in your architecture. Matt. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
