Re:Multi-core HTTP Server with Node.js
by alecco on Monday July 19, 2010 @05:59PM
(#1530317)
You can write a module to glue nginx and V8. Many people've done it. It takes less than 400 lines of code and a lot of it is nginx typical module code. (The problem is more about the lack of nginx online help, perhaps.)
Yes. But the big performance issue still is hitting the database and disks. There's no point in having a super fast web server if the DB is dog slow like the vast majority of databases out there. Including the NoSQL bunch. They are not fixing the issue of latency vs. scalability vs. reliability. For that they need to address many uncomfortable problems of current hardware architectures. This is the elephant in the room.
[ Parent
| on HN ]
Re:Multi-core HTTP Server with Node.js
by IsaacSchlueter on Saturday July 31, 2010 @02:05PM
(#1564052)
Well, at least it's an elephant we're all talking about a lot. It's not as if anyone's ignoring that.
If your DB is dog slow, you can still handle wildly high concurrency with node. It's just that the user will feel the slowness, and your DB will struggle. But at least your server won't be unable to serve requests while it's waiting for IO.
Of course it's still on the developer to architect their system for success. Node just takes one unnecessary bottleneck out of the equation.