Re:Migrating from AWS to Fly.io
by mrkurt on Tuesday January 03, 2023 @09:17PM
(#34241109)
I'm not completely averse (we've done this before!), it's just not how I think the world should work. If we hold out, and the future Fly cloud has a better-than-RDS Postgres option, it will be worth it. If we build our own managed Postgres, no one better is going to bring their stuff to our platform. Same with MySQL.
[ Parent
| on HN ]
I'd trust a first-party managed postgres built by fly more than a third-party one.
Re:Migrating from AWS to Fly.io
by belmont_sup on Wednesday January 04, 2023 @12:08AM
(#34242246)
I like their strategy of outsourcing what they’re not best at to the best. They partnered with upstash, and now they’ve got a new feature almost immediately. Sure there’s a lot of vetting, but wrapping products is common.
I’d be happy if they can wrap Neon’s serverless postgres service into their networks somehow.
Neon CEO here.
We are working on becoming first party service on several major problems now. We will be happy to provide this for Fly. Kurt and I have been chatting.
Fly wants cross region replication which is coming soon. Once it's there we can integrate.
With that Neon is still on AWS and can be close to Fly, but not run on Fly servers. It's relatively straightforward for us to run on Fly, but the S3 part will still be Amazon.
Re:Migrating from AWS to Fly.io
by robertlagrant on Wednesday January 04, 2023 @05:02AM
(#34243890)
This sounds like a match made in heaven.
Re:Migrating from AWS to Fly.io
by belmont_sup on Wednesday January 04, 2023 @11:36AM
(#34247739)
Fantastic, nikita! Hope all goes well.
Re:Migrating from AWS to Fly.io
by ignoramous on Tuesday January 03, 2023 @10:33PM
(#34241692)
> I'm not completely averse (we've done this before!)
For those out-of-loop: https://news.ycombinator.com/item?id=7382151