One thing this article is missing is the arbitrary "400MB slug size" that heroku limits your application to if you want to deploy.
FWIW that's a "soft limit". I've deployed slugs over that limit without trouble. Idk if they have a hard limit.
Why companies move off Heroku (besides the cost)
191–200 of 230 posts
Re: Why companies move off Heroku (besides the cost)
#192Earlier quoted context omitted.
correct. RDS does not even let you do a true, vanilla postgres backup to s3. the lock-in is complete
You can easily use pg_dump to do a "vanilla" backup to s3. Its a managed db service but if you wanted to run your own you can extract your data and move to a new db. The lock is not "complete" you are acting like you can't even extract your data.
Re: Why companies move off Heroku (besides the cost)
#193As someone that was there at Heroku after the acquisition, I don't think you can state that since the acquisition it's been consistently downhill. There isn't much debate that things have stagnated in the last 5-7 years which is a longer story on why probably. Some examples of innovation that happened and were launched after the acquisition: buildpacks (at the time of acquisition Heroku was still Ruby only), Heroku P…
I think the most interesting part of this is the PaaS disaggregation. Heroku built an exceptionally good Postgres service. They could not have done that with multiple DBs. Even their redis is pretty meh. People like us (Fly.io) will end up either building very mediocre DB offerings or collaborating with DB companies (like yours: https://www.crunchydata.com/products/crunchy-bridge/ ) to ship stuff that's substantially…
Re: Why companies move off Heroku (besides the cost)
#194I'm historically a huge Heroku defender. Been using it for a decade now, and my company still uses it despite being quite large and getting a lot of traffic. It's always been a great product and the early Salesforce days they DID ship a ton of new stuff and improve rapidly (despite a narrative that they didn't). Like, it got REALLY GOOD the years after acquisition. That being said... it's insane that we haven't been…
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…
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 but it works so nicely !Interesting side story, about 10 years ago I was employed by a "big"(for me at least) price comparison service, and for 5 of the 7 years we use a simple bash script to deploy most of our API's and frontend.
Everyone agreed (it's the wrong way) to do it but no one wanted to dive into the alternatives.
We even found a bug where there were some race issues (some weird service configs) when we deployed that it only worked every 2nd time ? horror
So we just "always deployed twice"... since it's was super fast !
Re: Why companies move off Heroku (besides the cost)
#195As someone that was there at Heroku after the acquisition, I don't think you can state that since the acquisition it's been consistently downhill. There isn't much debate that things have stagnated in the last 5-7 years which is a longer story on why probably. Some examples of innovation that happened and were launched after the acquisition: buildpacks (at the time of acquisition Heroku was still Ruby only), Heroku P…
I mean if this is how you're going to treat your customers, then good luck! I'm yet to try out railway.app and..looks interesting to say the least.
Re: Why companies move off Heroku (besides the cost)
#196For 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.
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 ?
Re: Why companies move off Heroku (besides the cost)
#197Earlier quoted context omitted.
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.
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 ?
Re: Why companies move off Heroku (besides the cost)
#198We'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…
Absolutely ! It almost get to the point now where you need to be a "level-100+ aws " to know what and how to do it.
PS. Focusing JUST on UI/Ease-Of-Use. Look at hetzner cloud. I just love their cloud-ui ! (I feel that german efficiency in there - lol )
It reminds me of FreeBSD VS Linux. It's so less complex and the whole system(ui) just "fits" in your head :)
I love their UI in comparison to their competition. Like say Scaleway which I like very much and use every day but their (Scaleway) UI is looking like
"12 year old girl's bubblegum-and-unicorns party theme"
PS2. Now if only Hetzner has a default FreeBSD install image for their VPS
Re: Why companies move off Heroku (besides the cost)
#199Earlier quoted context omitted.
correct. RDS does not even let you do a true, vanilla postgres backup to s3. the lock-in is complete
You can easily use pg_dump to do a "vanilla" backup to s3. Its a managed db service but if you wanted to run your own you can extract your data and move to a new db. The lock is not "complete" you are acting like you can't even extract your data.
RDS makes it very inconvenient to do anything other than use their managed services.
because RDS backup data storage is VERY EXPENSIVE even compared to s3. this is very deliberate.
Re: Why companies move off Heroku (besides the cost)
#200Earlier 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.
If your resources are required, then they should be committed. If you want persistent cache, there are options both inside and outside Heroku.
I think I agree with you though - it's weird for me to have code on Heroku, and then log in to AWS, to put stuff in S3 manually.