Platinum Partner
architects,cloud,javascript,node.js,heroku,nodejitsu

Heroku vs. Nodejitsu for node.js

It all started when I wanted to try out node with websockets with ws and found that -- strange but true -- Heroku doesn't support node's ws. It does, however, support socket.io, which internally uses ws for its client. Well, Heroku is an old horse focusing on many programming languages.

On the other hand, Nodejitsu is all node.js clouds. Simple. Scalable. Enterprise-ready! Deploying apps here feels like you're working on localhost.

I'll give you a better picture of why Nodejitsu is a clear winner for node.js! Let's see the workflow of creating and deploying nodejs apps with these two contenders:

First up, Heroku --

Steps to deploy node to Heroku:

  • Create a node app and test locally.

  • Add a Procfile with web: node server.js

  • Install and setup heroku gem.

  • $ heroku app:create <app_name>

  • $ git push heroku master

  • heroku ps:scale web=1

"Heroku free version has no support for ws yet...so holding it for now"

Nodejitsu FTW!:

Steps to deploy node app to Nodejitsu:

  • Create an account at nodejitsu

  • Follow the mail that you get from them i.e : sudo npm install jitsu -g ; jitsu users confirm <user> <uniq_id>

  • Now create any node app, say in the dir called myapp

  • And finally jistsu deploy that's it!

So basically after you're logged in, it's just jistsu deploy and it supports all npm moduels!

You still think Heroku is a winner? Anyway, that might be relative, I'm not against anyone, just expressing my thoughts.

I quote :

"Support: I was blocked for 10.5 hours on a tiny bug with Heroku that ensured I couldn't db:push to sync up my databases. It took an awful lot of effort to get in touch with someone. With Nodejitsu, that's completely different. They're heavily active in IRC and put up with all my inane questions. In #heroku, I just get herobot spamming every ten minutes."

I've had the same experience.

Published at DZone with permission of {{ articles[0].authors[0].realName }}, DZone MVB. (source)

Opinions expressed by DZone contributors are their own.

{{ tag }}, {{tag}},

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}
{{ parent.authors[0].realName || parent.author}}

{{ parent.authors[0].tagline || parent.tagline }}

{{ parent.views }} ViewsClicks
Tweet

{{parent.nComments}}