Live data from Hacker News

Why companies move off Heroku (besides the cost)

blog.porter.run

151–160 of 230 posts

Re: Why companies move off Heroku (besides the cost)

#151
Awhile ago, my hobby Heroku site was shut down for vauge "violation of policy" reasons. Turns out it was an automated bot.

When they brought it back up they kept breaking this and that... I kept having to re-open tickets.

I'd really like a free alternative. (Or maybe I should figure out how to host from my NAS.)

Re: Why companies move off Heroku (besides the cost)

#152
Heroku is my tried and true. I've likely done thousands of deploys over the years and have never had one go bad or leave my app in a bad state. I have rolled back an app a few times due to bad configs and it was always quick and left me with a huge sigh of relief.

That being said, they are very stagnant on features. A dyno has operated the same way, at the same size, at the same price for like 10 years now? The main features I would like to see are auto-scaling for all dynos and IPs that allow you to restrict database traffic. Render looks promising in that department and could likely get business from me if Heroku doesn't change in the next couple years.

Re: Why companies move off Heroku (besides the cost)

#153
post #148
post #19

Earlier quoted context omitted.

https://render.com is my favorite in this space

How does render compare to Netlify? They seem fairly similar.

More backend focus - databases, cron, backend apps - while keeping the netlify-experience frontend goal

Re: Why companies move off Heroku (besides the cost)

#154

We're big Heroku customers; despite that, I largely agree with the points in this article and there's a voice in the back of my head asking every few months "is this worth it?" Whenever I research the new crop of Heroku clones (the one being hawked here, and others) the pitch is always "it's just like Heroku but you can run it in your own cloud". It's mind-boggling to me that none of the clones understands that I DON…

AWS’s ECS Fargate with Aurora Serverless and AWS CA certificates is close.

I think AWS App Runner (+ Aurora Serverless) could be even better. From what I can tell, App Runner is supposed to be the successor to Elastic Beanstalk and AWS's PaaS offering. App Runner seems a little immature right now (it launched last year and was missing some key features on launch), but it is actively being developed.

I've always been hugely disappointed that AWS doesn't have a better PaaS offering, given Heroku's languishing, and I was hugely disappointed when App Runner launched and was missing some key features... but there is at least a little hope that it's improving.

Re: Why companies move off Heroku (besides the cost)

#155

Earlier quoted context omitted.

* It was automated. Now it requires someone to pay attention and do it. You need to check if CI passed, and pull, and be sure you pulled the version that passed CI (maybe someone pushed since then). * Review apps, the only remaining heroku "killer feature", do not work at all. The fact that this has been broken for 2 weeks tells you everything thing you need to know about the state of their code base, and the resourc…

Tip for your first point: make the CI server push to heroku.

^^ This.

Re: Why companies move off Heroku (besides the cost)

#156

The year is 2022 and still no HTTP2 support. https://help.heroku.com/JAOCNZ25/does-heroku-have-plans-to-s...

Yes, this is :(, but you should be serving all your static assets through a CDN, which will have http2. I can't think of a scenario where I would want to serve anything other than the dynamic content off the heroku server. I don't think http2 buys you much there. So you should be able to get away with at most 2 requests - one to the heroku server, and one to the cdn.

Need http/2 for grpc, which is certainly gaining popularity these days

Re: Why companies move off Heroku (besides the cost)

#157
post #131

Earlier quoted context omitted.

I'm curious about what "substantially better than RDS" means. RDS has been good enough for me for quite a while. Does it only matter once you get to a certain scale?

RDS runs pretty well! It's just irritating to use. The good DBaaS give me a lot more power. This is true for Heroku PG, PlanetScale, Supabase, and Crunchy Data. Some of them let me fork a DB to run a PR against, some give me app level features that save me code, etc. Most modern hosted DBs also let you run your own replicas. I'm not really complaining about how well RDS works when your app is connected to it and it d…

What do you mean? RDS lets you run replicas

Re: Why companies move off Heroku (besides the cost)

#158

First off, I would strongly disagree with the idea that Heroku post-acquisition was stagnant. As well-said elsewhere, tons of product was shipped to industry-best standards: postgres/dataclips, Heroku Connect, buildpacks - as well as introduction of CI and preview apps. But it's clear that in the post-k8s and post infra-as-code world there's been a surge in new options for how teams manage their infra and DevOps tool…

I feel like you are on to something. I’ll keep an eye out for AWS support.

Re: Why companies move off Heroku (besides the cost)

#159

For all heroku's frustrations (and I agree with all of them in the article), it is still the only thing that "just works" for a standard monolith web app. Heroku is not cheap, but it is still cheaper than a couple full time employees + aws. It is really too bad they aren't innovating - they are just burning up their 10 year lead in the space. I wouldn't start a new project on Heroku - not because of the cost, but bec…

It blows my mind that they don't provide an object store. Almost all web apps in my experience need an object store of some kind.

Yeah I agree. Having to have Heroku and AWS simply because of this missing feature is annoying.

Re: Why companies move off Heroku (besides the cost)

#160

We're big Heroku customers; despite that, I largely agree with the points in this article and there's a voice in the back of my head asking every few months "is this worth it?" Whenever I research the new crop of Heroku clones (the one being hawked here, and others) the pitch is always "it's just like Heroku but you can run it in your own cloud". It's mind-boggling to me that none of the clones understands that I DON…

Yes. Every. Single. Time.

I’ve been using Heroku since 2013. In both a hobby and professional manner. I was even one of the first employees at a Healthcare specific Heroku clone (before we expanded to other products). I’ve been extolling the virtues of Heroku for nearly a decade.

Whenever something new comes out there’s always some critical piece that’s missing. The simplicity and the “it just works” factor of Heroku cannot be understated.

Take logging for example. Let’s say I want to add papertrail to a Heroku project. How do I do that? I click one single button. Heroku handles the environment variables, standing the logging container up, making sure I have access to it, etc. I don’t have to do literally anything to get it to work. The same goes for any add-on or service. Need Redis? Sure! Just click this button. That’s quit literally all you need to do.

Compare that to AWS, which is a nightmare of config hell, permissions, roles, policies. And that’s just getting it created and stood up. Not to mention maintaining it.

Post reply on HN