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

101–107 of 107 posts

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

#101

Post by coupdejarnac »

DangitBobby wrote: post #88
coupdejarnac wrote: post #68

Earlier quoted context omitted.

I don't really care to hear what they have to say on the subject at all. They're freeloaders.

In the article, it says they use Heroku for work and hobby projects. I imagine, like many developers with projects on the side, they try out new tech or platforms on the side and advocate for it at work. In this case, I imagine they used Heroku for hobby projects because it was free and brought it to work (where they could switch seamlessly to a paid tier when usage demanded it) because they liked the platform. On He…

I think it's reasonable to say that having 25 projects on free tier is excessive. So, be outraged all you want.

Can I borrow your car? I'll only put 20k miles on it, no big deal, man! Oh you won't? Do you know where I can use a car for free?

And you're defending this kind of nonsense.

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

#102

Post by nullzzz »

coupdejarnac wrote: post #39

I have zero sympathy for these guys, nor for anyone else running their business on free tier infrastructure. This is the kind of customer nobody needs.

Post author here. The article is about alternatives for running your hobby projects. I agree that it doesn't make sense to run, or expect to be able to run, your business applications on free tier. We will keep on using Heroku's great services from now on as well.

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

#103

Post by nullzzz »

dasil003 wrote: post #26

This looks like a serious agency, so I'm stuck on the question of why the free tier is so important to them versus simply paying for Heroku. Surely doing a mass migration to a new PaaS just to claim a small per-project savings is a dubious proposition given the inevitably of a future rug-pull from wherever you migrate. On the other hand, if you're an individual with a bunch of small projects and you want to host them…

Post author here. We are of course using paid dynos for any business applications. Free tier only makes sense for hobby projects and quick experiments. There's no free lunch in the long run.

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

#104

Post by nullzzz »

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…

Post author here. I agree!

Did not mean to imply that Dockerizing applications is a bad thing - actually even pointed out that "it's not so hard". Just wanted to point out that writing one takes some effort and therefore Fly.io is not a drop-in replacement for Heroku.

Container based deployment is a great thing to have and definitely a skill worth learning.

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

#105

Post by matthewcford »

franciscop wrote: post #98
jorams wrote: post #95

Earlier quoted context omitted.

> Or do you mean it's the same in Fly.io? If it auto-detects Node.js (through package.json), Indeed the docs[1] say Fly automatically detects a Node.js project, so you don't need to create a Dockerfile. [1]: https://fly.io/docs/languages-and-frameworks/node/#launch-th...

> At this point, flyctl creates an app for you and writes your configuration to a fly.toml file. You'll then be prompted to build and deploy your app. Once complete, your app will be running on fly. Well it still creates a fly.toml for you, which is still a new config file that I have to maintain across projects.

You update the toml file once (e.g if you have a release step), and then don't touch it again. Its more powerful than Heroku, so with that it gives you the option of adding additional config options.

I mean it even creates the basic file for you, I'm not sure what the issue is?

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

#106

Post by matthewcford »

LAC-Tech wrote: post #74
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…

Fly.io seems like the easiest way to get a docker container running publically. I had a look at the AWS equivalent (can't remember the name), and it was a cluster fuck of complementary services in the tutorial. Wish more cloud providers would focus on helping with existing open source tech, rather than trying to suck you in.

AWS Copilot https://aws.github.io/copilot-cli/

And it's a nightmare compared to fly.io

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

#107

Post by x86hacker1010 »

larrymyers wrote: post #64
x86hacker1010 wrote: post #56

Earlier quoted context omitted.

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've found nomad far easier to operate and maintain, and conceptually it's easier to wrap your head around as well. It helps that nomad is just responsible for container orchestration, that's it. You can use whatever you want for ingress routing (I really like traefik).

That’s good to hear. I also like Traefik but I used some Traefik ingress controller on K8s. I really just want an orchestration tool for my containers and nothing else since NGINX and Traefik have nice enough abstractions. Thanks y’all.
Post reply on HN