Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Life after Heroku: What's a dev to do?

reaktor.com

Post reply on HN
Print view View original

51–60 of 107 posts

Re: Life after Heroku: What's a dev to do?

#51

Post by theonething »

lis wrote: post #18
mscarborough wrote: post #13

Interested to hear what the paying business customers who migrated away from Heroku think about their new home and the process to move to Fly/Render/Digital Ocean/whatever?

I've migrated one larger project with several containers / databases to AWS Fargate / RDS and a smaller one to Scalingo [0]. In both cases, I'm happy with how it turned out and the migration went fine. One of the main drivers behind the decision was that Heroku required us to move to the Enterprise tier to run private databases. If the architecture of your application is not too complex, I would suggest trying Scalin…

> Review Apps feature to automatically launch environments from pull request worked well for our workflow.

Render has this exact feature. They call it Pull Request Reviews. Was it not around when you were evaluating?

Re: Life after Heroku: What's a dev to do?

#54

Post by nurettin »

larrymyers wrote: post #35

The article calls out having to learn how to create a Docker image for Fly.io as though it's a bad thing. I consider it a huge bonus if you like taking advantage of free tiers for services. The whole point is that if you're going to take advantage of a free tier you should do so in a way that switching is trivial. Docker goes a long way to achieving that. I personally just pay $10/month to Linode and self host these…

Your post made me realize that I pay more to digitalocean for a 2gb ram instance. I guess roles got reversed.

Re: Life after Heroku: What's a dev to do?

#55

Post by js4ever »

charrondev wrote: post #41
ysavir wrote: post #36

My biggest take away from trying to find a Heroku alternative is that Heroku is late to the game of charging for a basic app. Other service might be free, but seem to have some sort of catch--only static, or requires a certain infrastructure, or whatever else--and only Heroku had the unopinionated free tier. And while I haven't used their competitors, I'm skeptical they can match Heroku's interface, CLI, add-on ecosy…

I’ve found Vercel to work well for my personal projects. It’s supports dynamic applications and static ones, custom domains, CI for deployment and has a useable CLI all available on its free tier.

It's not comparable, you have to rewrite your backend to make it work with vercel

Re: Life after Heroku: What's a dev to do?

#56

Post by x86hacker1010 »

larrymyers wrote: post #35

The article calls out having to learn how to create a Docker image for Fly.io as though it's a bad thing. I consider it a huge bonus if you like taking advantage of free tiers for services. The whole point is that if you're going to take advantage of a free tier you should do so in a way that switching is trivial. Docker goes a long way to achieving that. I personally just pay $10/month to Linode and self host these…

Can you speak to Nomad vs K8s for side projects?

I’ve deployed K8s in the past but was curious if Nomad is lighter/easier

Re: Life after Heroku: What's a dev to do?

#57

Post by creatonez »

chimeracoder wrote: post #8
josephcsible wrote: post #6

Earlier quoted context omitted.

It feels like a bait-and-switch and the "heroin dealer" model to give something away for free just long enough that people become reliant on it, and then suddenly make it be paid.

> It feels like a bait-and-switch and the "heroin dealer" model to give something away for free just long enough that people become reliant on it, and then suddenly make it be paid. Heroku's free tier has been incapable of running a 24/7-accessible webserver for many years, nearly a decade[0]. At this point, if anyone is reliant on it, it's almost impressive that they've managed to get by for so long without either p…

If you verify with a credit card, a single dyno can run for as many hours as you like -- it can perpetually serve HTTP requests for years and years -- but it will be automatically turned off every few hours, with some latency on the first request to boot it back up.

I would say this kind of free tier is quite powerful. It even had free Redis and PostgreSQL. But it had some horrendous periods of downtime and bugs that affect the paying customers just as badly. So ironically the free Heroku experience in 2022 leads you to the conclusion that it's the worst service you could pay for, but the best service you could mooch off of (aside from fly.io and similar) -- which may be counterproductive for Heroku's marketing.

Re: Life after Heroku: What's a dev to do?

#58

Post by torvald »

x86hacker1010 wrote: post #56
larrymyers wrote: post #35

The article calls out having to learn how to create a Docker image for Fly.io as though it's a bad thing. I consider it a huge bonus if you like taking advantage of free tiers for services. The whole point is that if you're going to take advantage of a free tier you should do so in a way that switching is trivial. Docker goes a long way to achieving that. I personally just pay $10/month to Linode and self host these…

Can you speak to Nomad vs K8s for side projects? I’ve deployed K8s in the past but was curious if Nomad is lighter/easier

I can share some articles later, but Nomad is a ten-fold easier.
Post reply on HN