Hacker News new | ask | show | jobs
by pyentropy 1371 days ago
> point-in-time backups through the web UI

Is `fly postgres create --name restoredDb --snapshot-id backupId` that hard that's it's a deal breaker?

> support for Heroku buildpacks

I haven't tried it but there's some buildpack support: https://fly.io/docs/reference/configuration/#builder

1 comments

It's not a managed database, if things break at 3am, you have to fix it yourself. The buildpacks are an afterthought using third-parties. A real evergreen solution will track the official Heroku solution (since fly.io doesn't even bother to document their buildpacks) to the nearest day. The whole point of the P in PaaS is that somebody else does the DevOps. If I have to do so much DevOps, then there's no point in adopting Fly. I am getting the impression that users here only care about their shiny blogposts and content marketing, versus the actual experience as a business user.
I'm going to make a point here that might be contentious: you are asking for Heroku. Heroku is going away because it no longer works as a business.

We are not Heroku. It is ok for you to not like what we're doing. We're building something different. We've never even _said_ we were a Heroku alternative, we just liked their UX for deploying apps and decided to roll with something similar.

> Heroku is going away because it no longer works as a business.

I would rather say 'It no longer works as a business for Salesforce.'

While I can't agree with melony on buildpacks (shipping OCI containers straight from our CI to Fly has been a game changer), I do agree on the importance of fully-managed databases.

Our app has two components, a backend on Heroku and distributed frontend on Fly. The backend relies on a managed database, and I have not had to touch it in 6 years. Heroku does a great job providing confidence that the managed database will Just Work. The current Fly Postgres offering doesn't provide this confidence.

I also agree about the importance of fully managed databases!

We shipped "automated" Postgres because we couldn't get any fully managed DB providers to pay attention to us when we were small. I expect we'll have an option running on Fly infrastructure in the next six months.

Our Redis is fully managed, so you can get an idea of how it might play out: https://fly.io/docs/reference/redis/