Ask HN: Are you leaving Heroku?
71–80 of 114 posts
Re: Ask HN: Are you leaving Heroku?
#72I am not very familiar with any of these, but here is the short list of things I've compiled from past HN threads, that might be alternatives to heroku that provide similar affordances to heroku. Most of them I have done no more than look at the website and determine that, yeah, it was similar to heroku for my personal criteria of what makes something similar to heroku. (Some things suggested in past threads did not…
Re: Ask HN: Are you leaving Heroku?
#73I am not very familiar with any of these, but here is the short list of things I've compiled from past HN threads, that might be alternatives to heroku that provide similar affordances to heroku. Most of them I have done no more than look at the website and determine that, yeah, it was similar to heroku for my personal criteria of what makes something similar to heroku. (Some things suggested in past threads did not…
I can only speak about render.com which I've seen recommended several times. I was thoroughly unimpressed. Heroku is my go to when I want to spend no more than 5 minutes getting a microservice deployed. Otherwise I would use DO. Render seemed to be the longer and clunkier experience of DO without the benefits of DO.
Re: Ask HN: Are you leaving Heroku?
#74Earlier quoted context omitted.
Heroku's Postgres is still very good. If I were looking for "very good Postgres", I would go straight to Crunchy Bridge. I don't think a PaaS is going to get anywhere near that level soon (and I work on Fly.io, so I know we're not). Building a good PaaS and building an amazing managed database service are two problems that overlap less than you think. The moment we can get Crunchy Bridge or someone at a similar level…
Kind of becoming a sidebar, but I'm curious if Amazon RDS Postgres counts as "managed postgres"; or, more to the point, what something like Crunchy Bridge gets you over Amazon RDS. (I have used neither Crunchy Bridge nor Amazon RDS, so this is an actual question, not a challenge! I have used Heroku postgres as well as self-hosted postgres)
Another big area is tooling we're building in to help app developers. Things like health reports for your database, built-in audit logs, simple SSO integration are just a few things that you now don't really have to think but can benefit heavily from. Overall we're a pretty big parallel to Heroku Postgres, with more to come (I wrote about some of that vision here - https://www.craigkerstiens.com/2022/05/18/unfinished-busines...).
Re: Ask HN: Are you leaving Heroku?
#75Earlier quoted context omitted.
Are the things you feel are missing from fly/render, or is it just a case of it not being worth switching an already set up project?
Fly.io doesn't track Heroku buildpacks nor does it recommend buildpacks as a first class workflow. Buildpacks are very underdocumented. The official tutorial and guides pushes Docker as the "preferred" workflow. Docker is nice for environments like Rust/Go/when you have additional dependencies. For Ruby/Python/Node buildpacks are a lot easier. Your typical Heroku tutorial says "use cedar-XYZ pack for Python Z and eve…
Our primary benefit over Heroku isn't "the simplest possible DX". Heroku has that nailed! It's running apps close to users, easily scaling them up and out over the globe. I like us a lot (but then I would) for simple apps that will never need global scaling, but nobody at Fly.io is telling you that we've somehow obsoleted Heroku!
I'm confident that we'll get to parity with Heroku on DX; it's a thing we're serious about. But Heroku has had a long, long time to get these details right, and we're working on other things too. Give us a bit. :P
Re: Ask HN: Are you leaving Heroku?
#76Notes here: https://gist.github.com/ianchesal/5c96c566ab99b60c2c557711fa...
Re: Ask HN: Are you leaving Heroku?
#77Main reason for the move was pretty simple, we just needed more control over our own infrastructure and Heroku wasn't able to offer that. Things like HTTP2 support, access to load balancer configurations, timeout settings, different auto-scaling options and better monitoring are first things that come to mind.
We are now using AWS directly (EKS, RDS, Lambda etc) and even though the move itself did cost a bit, I wouldn't say monthly costs went up too much (but it's bit hard to compare as we're using more services at AWS and scaled up right after migration).
Basically, we just grew out of Heroku.
And personally I wouldn't choose them again even if opportunity appeared.
Re: Ask HN: Are you leaving Heroku?
#78Re: Ask HN: Are you leaving Heroku?
#79Re: Ask HN: Are you leaving Heroku?
#80Had a hobby project on heroku that I've moved to render.com pretty painlessly. It's a simple rust (actix + sqlite) project. I now have a go (gin + sqlite) project that is intended to replace the rust project that I also plan to set up on render. Overall it's been incredibly pleasant & I've had no issues. To be clear though, these are very small/cheap projects between friends so I haven't needed to evaluate costs (bey…