“There are two types of coders out there: 1) those who haven’t used Node.js yet and 2) those who love it.”
With other languages and development platforms you scale it up by breaking your code into multiple threads of execution. And in those other languages you have to manage inter-thread communication and timing. In the Node.js world, though, you scale your app by having something bring up another instance of your main app itself.
Hosting a Node.js App
This new model of scaling matches nicely with a variety of cloud virtual computer providers such as Amazon and Microsoft. Even better, a secondary market of Node.js platform providers like OpenShift and Heroku provide a space for your application to be hosted. (Originally, you would have to create a virtual computer at Amazon, for example, install all the dependencies to run everything and then add your Node.js app. But now, a provider like Heroku assumes that you have a Node.js app and they take care of the prep-work for you.)
If you haven’t already done so, check out Red Hat’s OpenShift website as well as Heroku. Both offer a (typically) free tier if you accept the scalability defaults. Both work quite well for hosting a Node.js application. I would say that both sites offer good Getting Started documentation. I will say that I found the Heroku site to be slightly easier as a beginner. I’m currently hosting one Node.js app on each of them and am happy with both providers. Note that if your app needs additional “always on” (also known as “worker”) apps then you need to fully understand each provider’s pricing model before getting settled into either arrangement. You might easily incur an approximately $50/month fee for such an app. Otherwise, the base scalability of both providers is essentially free.