Live data from Hacker News

Why companies move off Heroku (besides the cost)

blog.porter.run

201–210 of 230 posts

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

#201
post #52

Earlier quoted context omitted.

What kind of workflow are you trying to fit? My impression is that this lack of 'instance storage' is by design, as well as other constraints that can be mapped to these: https://12factor.net/

I imagine Heroku would say the same, and thats fine. We deploy a bunch of Rails apps, backed by Postgres, via Heroku and most of the time what we're doing fits neatly into the 12 factor definition. However what happens if you're doing something that doesn't really fit that definition. For instance we have a Rails app with some background workers doing data processing. I would very much like to have these workers just…

My hunch is that if you try to build your solution with the constraints enforced by Heroku your system will be more resilient.

If it's about being easy to dump stuff to disk, using S3 or even Postgres for something like this could become easy after a few attempts. Another pattern that would come out of this exercise is trying to deal with that job in parallel by breaking it up into sub-tasks (many workers at the same time).

Anyway, too little context for me to flesh out a solution but the gist is that in general these constraints nudge you in a 'healthy' direction when designing systems.

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

#202

Earlier quoted context omitted.

At the time we would joke a bit that acquisitions would get some new very high priced domain. We even looked at getting the .app TLD for all Heroku apps to get their own .app domain. We ended up with our acquisition "gift" as Matz, which was great to see it support Ruby and the community given how Heroku couldn't have become Heroku without the Ruby and Rails community.

When you hire a celebrity programmer like that, what exactly do they end up doing? Do they actually have responsibilities in their role or is it more just to slap the branding on to them while they continue to do their own thing, whatever it may be? (in Matz case I would think he has more than enough full time work on Ruby itself)

Heroku/Salesforce essentially just picked up the salaries for Matz and part of his team to work on Ruby, with no other commitments as far as I'm aware.

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

#203

Earlier quoted context omitted.

Check Netlify Or Vercel Best scaling in their free plans Heroku hobby is a joke in comparison and hasnt been updated in a decade while all their addons have gotten less and less featured while costing more and more I host all my static assets on IPFS which practically nullifies the bandwidth limits of Netlify

Could you elaborate on how you use IPFS? How fast is it? Do you use use a pinning service?

I upload static assets to IPFS and add those static links to my project instead of having an "assets" folder.

IPFS is fast enough, I had these concerns too so I use a gateway for links as some of them cache files on their own CDN, for free.

Yes, I use a pinning service, I was extremely hesitant as many of them are just SaaS hosting like Pinata is and charge by bandwidth used, but there are free ones like https://web3.storage which for some reason is combining Filecoin and IPFS together for each upload and liveness/pinning.

Ironically, Pinata also acts as a gateway and can then be used for free if you want. But there are other gateways. Cloudfront has one but what it decides to cache is strange.

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

#204

Warning: There are a couple people in this thread mentioning products that they're investors in. I won't call them out expressly, but I think people should be direct about their incentive alignments. It's disingenuous and borders on astroturfing IMO. Background: Founder of Railway.app here. There's a lot of these companies popping up that offer a "Heroku replacement", and once you dive in, you realize you have to pay…

Personal criticism of Railway: every time I emailed Railway to request to be unsubbed from the newsletter and my account fully deleted without a trace no one ever replied (the unsubscribe link in the newsletter was broken). It left a really sour taste in my mouth.

Hey Emptysongglass,

Angelo here, Support Engineer from Railway. I am sorry to see you go from Railway and personally speaking, I wouldn't want my PII floating anywhere I wouldn't want it to be.

If you can email me directly: angelo (at) railway (dot) app with your username from HN with your account email. I would be more than happy to make things right here.

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

#205

Warning: There are a couple people in this thread mentioning products that they're investors in. I won't call them out expressly, but I think people should be direct about their incentive alignments. It's disingenuous and borders on astroturfing IMO. Background: Founder of Railway.app here. There's a lot of these companies popping up that offer a "Heroku replacement", and once you dive in, you realize you have to pay…

Railway looks really cool but what is the procedure if you want more than one of the same data store in my case one redis for cache and a second redis for aggregating usage metrics? Edit: I found a small bug, I can't link my discord and railway.app accounts because my github is < 180 days old, it says that I must enter billing information but I did that a couple hours ago. There's no way to post this message in disco…

Hey Beninsydney,

Angelo here (Support Engineer) from Railway. I was personally responsible for implementing the whole flow to link your account to post a support question. I apologize, I put those limits in place to help fight a recent wave of spam. If you can email me directly: angelo (at) railway (dot) app - I would love to answer any questions you may have.

In the meantime, I will be sure to make things right for your account. For others who might face the same issue as you, I will rectify the issue with the support flow moving forward.

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

#206
Losing GH automation did cost me exactly 20min. changing the alias from push github to push to both was trivial.

I think Heroku did the right thing, but Travis still hasn't responded and changed anything, whilst the exploitation is still going on. If only I got get rid of Travis in my GitHub integrations. Deleting the app and actions and hooks hadn't changed anything. Travis has no access anymore, but PR's still block on the not existing Travis CI.

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

#207

Earlier quoted context omitted.

Lol Whot ? Not trying to be a d*k or saying you are wrong, maybe I've only worked on simple-silly projects in my "medium'ish-long-career" so far but: Why do you say that ? Really interested ?

Where do you store things like images, PDFs, binary files etc involved in your web apps? Most CRUD apps in my experience involve some kind of artefacts that need to be stored in some way.

What if your artifacts are db-records ?

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

#208

Earlier quoted context omitted.

I'm in the same boat. We were in the process of moving off of Heroku a few months back. We had to pause that migration for a number of reasons, but the initial jump was to save some money. Now I'm kicking myself for not pushing the migration to completion. I've basically had to spend the last week recreating much of our deployment pipeline using a very complicated local deployment structure that only I can execute. I…

I feel your pain ! Never underestimate the value of a "good enough" bash scrip to deploy ALL your project(s). First (ok top 5) thing i do when starting any new project is quickly writing a "bash deploy script" which usually goes like this: *build-for-prod *post-build-steps (zips, uglify,spit-and-polish etc) *tar everything *scp tar-file to server(s), extract, restart xyz Sure it's unsexy as hell in today's world of b…

I did this sort of stuff for a time, it's even better if you link webhooks to your git provider and make those fire the actions directly in the server.

Once the script was set up to do all the build and deployment, we only needed to push to the release branch to load it, just as painless and with more or less the same underlying ideas that the easy CI/CD you get with providers like Heroku et al.

It still really pays off to know a thing or two about sysadmin nowadays, literally and figuratively.

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

#209

Earlier quoted context omitted.

Where do you store things like images, PDFs, binary files etc involved in your web apps? Most CRUD apps in my experience involve some kind of artefacts that need to be stored in some way.

What if your artifacts are db-records ?

Heroku already provides a managed database service using Postgres, so you're fine for that.

It's if you want to store any kind of user uploaded or generated binary or large content - images, PDF reports, audio files, videos, JSON documents, code, logs - all common things you may want to manipulate in a web service.

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

#210
post #131

Earlier quoted context omitted.

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…

we’re using aiven.io and quite happy, although hard for me to compare. you can port across clouds, which is reassuring if we need to switch. Otherwise their support was helpful debugging a couple of db issues (in our own code). Wonder how they compare in this matrix if anyone knows? no affiliation. just a customer.

aiven.io is quite good. They went broad instead of deep, so they're not as good at Postgres as the Postgres specific companies. But they're probably better Postgres than a PaaS can build by themselves.
Post reply on HN