We have a couple production websites on Heroku. One is a decade-old Rails app and the other is a Rails backend for a ~3-year-old site whose frontend is hosted on Vercel.
The decade-old app is still running great. We make extensive use of the Heroku CLI and some of the addons for databases and logging. The newer one isn't so heavily integrated into Heroku's features aside from the database. It was set up by a senior dev who's given largely free rein over his projects, but otherwise the company switched to DigitalOcean for new projects several years ago.
So my job is ~75% working with DO droplets and ~25% Heroku dynos. I didn't care either way, really, because at the end of the day my priority is the actual program. But the recent blowup with Heroku's GitHub integration was really painful, especially for our old app whose deployment process was deeply integrated with our GitHub repo. Once the outage had dragged out for a couple weeks, I started advocating to my lead for a move to DigitalOcean. The only reason we haven't done it yet is that we're a consultancy so we'd need to sell our very non-technical customer on a migration.
My points are 1) I think a lot of Heroku's business in 2022 comes from large, old projects that, for various reasons, are complicated to move elsewhere, and 2) Heroku is pretty much fine for those projects, aside from the recent issues that were thankfully resolved.
The decade-old app is still running great. We make extensive use of the Heroku CLI and some of the addons for databases and logging. The newer one isn't so heavily integrated into Heroku's features aside from the database. It was set up by a senior dev who's given largely free rein over his projects, but otherwise the company switched to DigitalOcean for new projects several years ago.
So my job is ~75% working with DO droplets and ~25% Heroku dynos. I didn't care either way, really, because at the end of the day my priority is the actual program. But the recent blowup with Heroku's GitHub integration was really painful, especially for our old app whose deployment process was deeply integrated with our GitHub repo. Once the outage had dragged out for a couple weeks, I started advocating to my lead for a move to DigitalOcean. The only reason we haven't done it yet is that we're a consultancy so we'd need to sell our very non-technical customer on a migration.
My points are 1) I think a lot of Heroku's business in 2022 comes from large, old projects that, for various reasons, are complicated to move elsewhere, and 2) Heroku is pretty much fine for those projects, aside from the recent issues that were thankfully resolved.