Heroku starts charging for app-deployment service | Hacker News Reader

Heroku starts charging for app-deployment service

venturebeat.com

16 pointspeter1234 comments

The checkout page is amazing. I really enjoy using heroku for some of my projects.

I can deal with the dyno pricing (I estimate its 1.5-3x linode or slicehost), but the db pricing is crazy expensive. Disk is (close to) free, and trying to use it to price discriminate moves me to Linode for a large subset of my projects. I'd greatly prefer something more tied to real costs, like query execution time, compute cycles, etc.

That's interesting feedback, thanks. Sounds like two different issues:

1. Database pricing. We aren't trying to sell storage space, that's not the value you're getting with a Heroku db plan. We would argue that the value is the instant, provisionless nature of the platform - radically faster deployment and scaling, and an environment that just works. So if those features of the platform aren't valuable to you (i.e. you want to provision, configure, and maintain the db yourself), and you're just looking for the best cost/MB, we're definitely not the right answer for you.

Let's say you set that comparison aside for a moment, and you took one of your apps that's providing value to you and selected a Heroku pricing configuration that fits the app's needs. Given the value of your app plus the value you get from our platform, is the total price worth it?

2. Pricing on query execution time, compute cycles, etc. Why is this appealing to you? Is it because those numbers make more sense to you, or because you think if we priced on those units it would make the platform less expensive for you?

Thanks again for your feedback - interesting stuff.

Howdy jamesheroku,

I have a great time deploying my app to heroku, and I've recommended your service successfully a number of times to other devs.

I even didnt get so mad when the service was offline for a bit yesterday, so that means you guys are really doing a great job! :)

I must say I'm afraid to have to pay for my hosting too soon, but you probably took that into consideration. :)

Is there any reason why not to run heroku rake db:migrate automatically on every push? ... i keep forgetting that.

take care. marcos toledo

Thanks Marcos. We were running db:migrate on push a long time ago for a while, but we ended that practice when serious production applications started moving on to the platform.

We found that running db migrations explicitly is very important for a mission critical production app.

Reply on news.ycombinator.com