[pkorzeniewski]

One question - does it support TCP sockets? I've evaluated a dozen or so Node.js hosting solutions and none (0, null, nil) supported TCP sockets. HTTP/S and WebSockets only. It's ridiculous - a TCP server is a major use case for Node.js and yet if you want to host it, you must configure and administrate your own server (on EC2 or whatever).

[aroman]

I don't think it's ridiculous. I definitely agree that acting as TCP server is one of the major intended use cases for Node.js, but in practice, I'd bet it's such a small fraction of use that most Node hosting companies decided it wasn't worth the financial investment to support that use case.

[Duhck]

We had the same problem. We actually wanted to use Heroku just for pre-production as it was the easiest to deploy / manage, but their TCP socket implementation is such a joke.

We would up just using AWS, and sunk a few days into dev / sys ops.

I would happily pay for a solution to this problem

[yannski]

Could you elaborate a bit on "their TCP socket implementation is such a joke" ? Are you talking about the Ruppell's Sockets addon ? What's your problem with it ? What could be an improvement to it ?

[pkorzeniewski]

I've also evaluated Heroku and the Ruppell's Sockets, so I can answer this from my point of view. The problem is that it's a workaround solution - all TCP traffic goes through an external server, which is unacceptable for any serious use case. How secure is that external server? What if it goes down? There isn't really anything that can be improved, other than Heroku natively supporting TCP sockets.