Hacker News Reader

Comment by dubcanada | Hacker News Reader

That seems a little weird. Let me put this in context, if I host my server on digitalocean for $5 a month or what ever, and let's say I have 1,000 visitors a day, which is rather small for a blog. And let's say I have a css file, js file, 10 images, and a website. That's 13 http requests assuming that nothing is cached. That translates to 390,000 requests a month (assuming 30 days), which is 90,000 over your 300,000 request limit. So for $50 a month I can't even do what my $5 a month server at digitalocean (and a free server at heroku if we want to compare it) can easily do?

You may want to rethink that.

View on HN

It's all relative. We save you time, and make sure your service is always up. We work with you through any pain points you have. If your server goes down, and you lose an hour of your time. You've already lost that difference.

You also assume nothing is cached, whereas only if those were all uniques would that be likely. Which is generally unlikely.

Our price is based around quality. Both the fact that we grow with you, and the fact that we strive to make every task you need to do, ridiculously easy.

Hmm.. I wouldn't be interested then. Seems like this is geared more towards the non-HN audience: people who need their hands to be held.

It's aimed at anyone who wants their hosting to be easy. It saves time and worry so you can just concentrate on your code without lots of hassle.

Hah, that's silly. If you wanted me to concentrate on coding,you'd help me with automated deployment, automated backup of my postgres db every night (even if it reaches 2 TB+ in space), etc, etc. Your solution isn't geared towards developers at all.

There's a wide variety of skills and wants from developers. The fact is; we have a user base of developers who do want us. And I personally, as a developer want us.

We have git automated deployment being released this week. And if your database is 2TBs, you want an Enterprise Solution.

You can currently snapshot your projects, in the same manner we do for failovers.

But we'll definitely keep your opinion in mind, thank you.

Depending on the website 13 requests is kind of small, 20-30 requests for a regular page probably more likely with maybe 3 or 4 that can be cached on an unoptimized site and the rest being image assets for that particular page and so on.

So with 300,000 I get something like 10,000-15,000 pageviews which is pretty much nothing.

What makes the "request" metric even more confusing is they say "Unlimited Data Transfer". Which means absolutely NOTHING if the # of requests is limited.

Not that I disagree, but if you were being charged per-request it would behoove you to use a CSS sprite sheet instead of 10 different images.

Reply on news.ycombinator.com