31–40 of 61 posts
I'd rather see the free tier be done away with and have the numerous AWS price decreases passed on to the actual paying customers.
Unfortunately, this kills my primary use case for heroku which is small personal projects. I have a dozen or so of them on the free tier right now. Heroku was great because I could throw them up for free and not really have to worry about hosting. Now, howerver, I have to weigh any given project against my overall budget of hours. If I put up my weekend project, do I need to kill that project from a few months ago? D…
Well you're using their PAAS for free. Ultimately a minority of paid users are paying for all the free users, it can't go on for ever.This is true for Heroku, as well as any PAAS that has a free tier right now.
If you use Heroku for hobby projects you don't need scaling and load balancing, you might need a DB on your instance so a dropplet at DO, or using EC2 makes more sense than paying 7$ for a immutable app on Heroku servers.
Finally, charging $20 for SSL was just highway robbery. Pure and unadulterated money grab.
I heard it was also sold at cost (of an ELB). https://twitter.com/johnbeynon/status/727375051331346432
Unfortunately, this kills my primary use case for heroku which is small personal projects. I have a dozen or so of them on the free tier right now. Heroku was great because I could throw them up for free and not really have to worry about hosting. Now, howerver, I have to weigh any given project against my overall budget of hours. If I put up my weekend project, do I need to kill that project from a few months ago? D…
Before you got 18 hours a day per app on the free tier (5 apps max)
Now you get 550 hours per month in total for all your free apps (so 18 hours a day for all your apps instead of per app).
It's clear they are trying to kill the free dynos but who can blame them?
Heroku is still good if you need simple scaling and load balancing for commercial projects. Heroku main selling point use to be easy deployment , but with Docker and solutions like that, it's not longer true.
I wonder if there is some room for an ultra cheap "micro" PAAS, like 2$/month per instance, with 250 Mb space and 128 Mb RAM or something like that. With the development of new, efficient languages such as Go or Crystal which can operate on tight configurations, I wonder if this model would be viable.
Unfortunately, this kills my primary use case for heroku which is small personal projects. I have a dozen or so of them on the free tier right now. Heroku was great because I could throw them up for free and not really have to worry about hosting. Now, howerver, I have to weigh any given project against my overall budget of hours. If I put up my weekend project, do I need to kill that project from a few months ago? D…
Now, if you're abusing the service, that's a different story...
"Flexible dyno hours" is some nice marketing spin. 550 hours a month works out to one application running 18 hours a day, whereas previously you could have an unlimited number of apps running up to 18 hours per day.
But you get 1000 free hours? (if you give them credit card data) If you just want one 24h-app + a bit that's better, if you can live with <=18h for all your apps it is worse.
TLDR; Before you got 18 hours a day per app on the free tier (5 apps max) Now you get 550 hours per month in total for all your free apps (so 18 hours a day for all your apps instead of per app). It's clear they are trying to kill the free dynos but who can blame them? Heroku is still good if you need simple scaling and load balancing for commercial projects. Heroku main selling point use to be easy deployment , but…
I have one hobby app. I use it, maybe, a hour a week. So that's a dyno that's on for, oh, maybe two hours a week, but more likely less (since the sleep timeout is, what, five minutes?). Barely makes a dent in my free hours.
When I actually want this useable, I bump it up a tier for the week or two, and we're done. Cost of a good meal.
Beside, we're only seeing the tip of the iceberg: Could be this is a change brought on by deeper changes in the billing system, such that this method ends up being simpler.
"Flexible dyno hours" is some nice marketing spin. 550 hours a month works out to one application running 18 hours a day, whereas previously you could have an unlimited number of apps running up to 18 hours per day.
Yup, basically killing most free apps, sad times.