Hacker News Reader

Comment by paulgb | Hacker News Reader

This looks promising. I wanted to go with Heroku for a node project a while back and couldn't because their feature-set didn't meet my needs (not to mention that your pricing is more affordable). A couple questions:

1. can your load balancer handle raw TCP load balancing, or is it always HTTP aware?

2. does it work with wildcard subdomains?

View on HN

1. We do not currently do raw TCP load balancing. It's HTTP and WebSocket load balancing. It's not an impossibility to do. Just haven't had a ton of people ask for it yet.

2. Yes you can use wildcard subdomains. You can then use different subdomains or wildcard on any project(s).

Just curious, but why do people on HN seem to prefer Heroku for Node projects? Is there a feature that I'm unaware of?

I'm a Nodejitsu user (and yes, its not free, so I get that) but Heroku doesn't even support Websockets at my last check.

People use what they're used to so most of the time that falls back to Heroku. I get that, I really do. Just want to make sure people know it's not the only option.

We use heroku at carddrop simply because it fits our requirements and we are comfortable with it. So far we haven't had any issues other than dynos idling (when we were on free account). We do serve quite decent traffic.

It was in fall of last year that I was looking at options and I don't think Nodejitsu was available on paid plans to the public at that time. In any case I don't think they supported the raw TCP routing I needed at the time.

Reply on news.ycombinator.com