Hacker News new | ask | show | jobs
by collectedparts 1233 days ago
This happened to me as well: projects with paid dynos but free databases, databases got nuked.

How Heroku missed this is beyond me. They managed to screw over paying customers in their broad attempt to stop freeloaders.

These are good accounts with credit cards on file. Why not just autocovert me to the lowest tier paid database?

FWIW I was able to get them to restore my databases. But I also had free Heroku Redis on one my projects and that, they assured me, is gone forever.

3 comments

I got "lucky" because I randomly checked the status page on my Heroku dashboard. It laid out which services were going to cost me after the switch date. I upgraded to the Eco tier and noticed that the DBs were still marked with a warning. So yeah, I would've been burned as well, had I not done that.
Right? Like just charge me and tell me. Also, while I still think it is way too aggressive how they deprecated free in general, at the very least... maybe uh... I don't know, let me know if you are going to delete my database? Absolutely insane.
Redis is a memory store, you're the one who fucked up treating a cache as a persistence layer.
Redis offers disk persistence [0]. Why can't it be used as a persistence layer?

[0] - https://redis.io/docs/management/persistence/

Redis offers disk persistence; Heroku's free Redis offering did not.
You can use Redis as a cache, but it's not fundamentally a cache.