Hi Leandro, Thanks for posting. I believe this is a valuable feedback - and to a point, possibly a valid concern that you're describing.
Small agencies and one-man teams have used the internet by providing the code which the client then hosts on a shared service and it's online, no matter where you pick it. The venerous LAMP stack was the go-to solution and still drives a huge part of the web. It would not be unreasonable to look for similar with a new platform, praised to be the new killer-app, allegedly so much better than PHP - but you can't even deploy it on a shared hosting service. However, I'd like to point out a few things that you may have missed, or haven't thought about. Or if you have, but have different conclusions than I do - please point them out as I'd like to know if I have flaws in my logic. Anyway, let's assume a few different aspects. Aspect one - costs. You say that you have a major problem with cost prices, with cheap node being 10x more expensive than PHP. I'd say that on average, cheap shared hosts offer something in the range of 1$ (give or take) for a shared host ,shared database or few, up to 10-100 MB or similar. The cheapest you can get away with for a Node app is free. If your app is stateless, if your traffic is so low that a cheap 1$ shared PHP host is good enough for you, you can likely fit all your requests in the free alotments of the more popular serverless/cloud providers. Even the database providers, e.g. MongoDB which is what MySQL would be in a LAMP stack, you have free offerings until a certain size - usually more than accomodating enough for low traffic websites. So I think it's a wrong assumption - hosting a node app can be affordable without "expensive" VPS services. But let's say your app is a bit more demanding, and you really need a VPS service. The cheapest *reliable* VPS providers that I know of, Scaleway and Hetzner, provide good and stable VPS nodes for a Node app for less then 2.5$ a month (2€). DigitalOcean, as a much more "famous" solution, or Linode or similar, cost 5$. Which is really, really affordable and reliable. Such a VPS can hold both a node app and a good database server, such as MySQL, without issues. If you want redundancy, you could have two and have replicated server. So, a VPS service itself is not that expensive. But the biggest problem here is the domain. What do you use PHP for, what do you use a Node app for? PHP is usually just a CMS, with maybe a contacts form or a comment box or similar. As soon as it gets used more seriously, you can't rely on shared hosting, and you have to go VPS route anyway. And Node, while it can also do that - in which case a serverless version is more than enough and will go a long long way before you need to start actually paying for some small monthly fee. So how do you use Node? What kind of projects you need to host? What are your strategies for it? What are your hosting strategies for PHP for the same projects? If you wanna make a comparison, you'd need to compare much more about how you approach your work. Otherwise, it really is back to the nineties, with all the nineties horror stories with it. Zlatko -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/9a146860-4987-4595-973d-231e65497a2d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
