Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Hosting for Node.js apps done right

evennode.com

Post reply on HN
Print view View original

21–30 of 42 posts

Re: Hosting for Node.js apps done right

#21

Post by yannski »

Duhck wrote: post #20
pkorzeniewski wrote: post #10

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).

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

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 ?

Re: Hosting for Node.js apps done right

#23

Post by cturhan »

sheetjs wrote: post #22
jain_chirag04 wrote: post #19

Irony is that their website is powered by PHP rather than node.

In general, how do you determine what software is running on the server side? None of the obvious links are to .php documents and the headers only indicate nginx

Look their cookies. You will see PHPSESSID meaning that session is provided by PHP.

Although, you can do the same with node session module it seems like php anyway.

Plus: http://builtwith.com/evennode.com

Re: Hosting for Node.js apps done right

#24

Post by _Soulou »

sheetjs wrote: post #22
jain_chirag04 wrote: post #19

Irony is that their website is powered by PHP rather than node.

In general, how do you determine what software is running on the server side? None of the obvious links are to .php documents and the headers only indicate nginx

A PHPSESSID appears in the cookie.

Re: Hosting for Node.js apps done right

#25

Post by iancarroll »

sheetjs wrote: post #22
jain_chirag04 wrote: post #19

Irony is that their website is powered by PHP rather than node.

In general, how do you determine what software is running on the server side? None of the obvious links are to .php documents and the headers only indicate nginx

There's a cookie called PHPSESSID.

Re: Hosting for Node.js apps done right

#26

Post by pkorzeniewski »

yannski wrote: post #21
Duhck wrote: post #20

Earlier quoted context omitted.

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

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 ?

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.

Re: Hosting for Node.js apps done right

#27

Post by cturhan »

marknadal wrote: post #8

Really neat to have FTP access for new JavaScript to NodeJS developers that don't know how to use git yet.

Just signed up and tried ftp access but seems like there is a problem. Most probably it's because of randomly generated ftp username

Edit: It's working but needs a time to finish deployment

Re: Hosting for Node.js apps done right

#29

Post by aroman »

pkorzeniewski wrote: post #10

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).

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.

Re: Hosting for Node.js apps done right

#30

Post by conradk »

This sounds like a joke to me.

1- "Hosting for Node.js apps done right": Like everything else is done wrong? That's just weird.

2- What does "designed for cloud" mean?

3- "Free support"? How gullible do you think we are? At 6e/mo, anyone that believes they're getting any kind of "Free support" is wrong. Or else this service is going to fail big time.

Now some constructive criticism: I see "FTP access". But as a dev, I would have liked to see something like FTPS, SFTP or better yet, SSH.

Post reply on HN