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.
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.