I think question that could be asked is, how long can any one tool, used correctly, defer the need to scale?
For some services, Node.js may give you more time and capacity. For others, Ruby or Python might.
You might need a static website, and you can develop it and push out the 'compiled' HTML to your server. For all the scaley goodness Node.js or whatever may seem to offer, for that purpose it'd never compete with NginX running a static server with appropriate caching.
Up until that point becomes visible on the horizon, you're just wasting time (and money) on a problem you don't or, if you're unlucky, might never have.
For some services, Node.js may give you more time and capacity. For others, Ruby or Python might.
You might need a static website, and you can develop it and push out the 'compiled' HTML to your server. For all the scaley goodness Node.js or whatever may seem to offer, for that purpose it'd never compete with NginX running a static server with appropriate caching.
Up until that point becomes visible on the horizon, you're just wasting time (and money) on a problem you don't or, if you're unlucky, might never have.