I can get a 4GB ram VPS for $10/m, which seems orders of magnitude cheaper than the popular options. What am I missing out on?
Also hosting a few private apps on a digital ocean vps using dokku[1] which is working pretty well so far.
(Disclaimer: Only used it for a simple app)
Where it sits, however, is only part of the problem!
I use plz[1] and instagit[2] in tandem via post-receive hooks to do the "deployment" bit, along with a service registry (closed-source, written on work time, boo!) like seaport[3] and a proxy based on httppp[4] to route requests to the right application.
---
1. https://github.com/deoxxa/plz
2. https://github.com/deoxxa/instagit
Obviously I don't have an opinion yet but my reason for giving it a try is that I've been told you get a free database instance in the same data center as your node instance, which is obviously good from a latency point of view.
I was talking to some of their employees at nodeconf this year and they explained that since Heroku only routes one request to an instance at a time, it essentially blocks on each request and you never get to actually leverage the concurrency of node.
I recently tried Heroku and Nodejitsu (business account) and ended up going back to Joyent.
Heroku
Nodejitsu
VPS
Linode
Digital Ocean
Amazon AWS
dotCloud
OpenShift
CleverCloud
NodeJS Cloud (by CleverCloud)Disclaimer: I'm one of the co-founders.
* Heroku
* ec2 using awsbox for dev with push deploys https://github.com/mozilla/awsbox
If you want SSL support and have a few apps then heroku can be a bit expensive, also monitoring is a paid addon.
Lots of choices at the moment which is awesome.
microsoft azure
heroku
digital ocean
linode
amazon aws
dotcloud
openshift
openstack
google appengine
can anyone tell me the pros and cons of each?I doubt there will be one who who tried them all though...
Might have to try Nodejitsu one of these days but the pricing kind of pains me when I think about how many low-traffic node apps I can host on a $5 DO.