Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Migrating from AWS to Fly.io

terrateam.io

Post reply on HN
Print view View original

71–80 of 189 posts

Re: Migrating from AWS to Fly.io

#71

Post by rendaw »

mrkurt wrote: post #53
rendaw wrote: post #47

Earlier quoted context omitted.

I've been trying fly machines with terraform and running into one bug after another: https://github.com/fly-apps/terraform-provider-fly/issues/12... https://github.com/fly-apps/terraform-provider-fly/issues/12... https://github.com/fly-apps/terraform-provider-fly/issues/12... I was really excited since fly seems dead simple, but I haven't gotten it running yet...

The Terraform provider was a one off project from the community. We haven't really focused on it in earnest yet, unfortunately. We ended up sponsoring it, but until we get Fly apps off Nomad I don't think we'll have the best terraform story.

Ah, well that explains it I guess.

Though, it's a "partner" provider and it's in your official github account, plus there's no notices saying it's not officially supported... it would probably help people if that were a bit clearer.

Re: Migrating from AWS to Fly.io

#72

Post by tptacek »

ckozlowski wrote: post #45
Octabrain wrote: post #16

Earlier quoted context omitted.

> RDS is ultimately a solution for people who look in the mirror and confidently say "you don't know how to run a database." I think this is a terrible oversimplification and something tells me that you haven't had to deal with a complex database setup from an operations perspective. RDS reduces a huge overhead in terms of operations (ha, backups, upgrades and clustering being the first ones that come to my mind). Be…

Spot on. RDS is a solution for people who look in the mirror and say "I'd rather be working on other things than running a database." (Disclaimer: I'm a TAM for AWS.)

In case it needs saying: Fly.io agrees with this! We didn't build our Postgres feature as a statement about the utility of managed Postgres; it's a statement about our size relative to AWS. :P

Re: Migrating from AWS to Fly.io

#73

Post by tptacek »

rendaw wrote: post #71
mrkurt wrote: post #53

Earlier quoted context omitted.

The Terraform provider was a one off project from the community. We haven't really focused on it in earnest yet, unfortunately. We ended up sponsoring it, but until we get Fly apps off Nomad I don't think we'll have the best terraform story.

Ah, well that explains it I guess. Though, it's a "partner" provider and it's in your official github account, plus there's no notices saying it's not officially supported... it would probably help people if that were a bit clearer.

Yep, this is a good note. Things got fuzzy, because we were so impressed by the person who took it upon themselves to randomly build a Terraform provider for us that we hired them.

Re: Migrating from AWS to Fly.io

#74

Post by tptacek »

sosodev wrote: post #56
mrkurt wrote: post #42

Earlier quoted context omitted.

Ah, thanks. We'll chase it down. We got a little behind over the holidays.

I really do appreciate it. Is there any way Fly could detect this? I know geo IP isn’t perfect but it seems like it could help you track this stuff by allowing you to compare edge location to the users location.

There probably is a good way to do this. Do you have thoughts on things we should do here? We have a code footprint in every region (and also in like 6 off-platform regions on other providers) for doing this kind of monitoring, and we're probably not putting it to the most effective use we can. Ideas would be most welcome.

Re: Migrating from AWS to Fly.io

#75

Post by joao »

tommoor wrote: post #59

Fly is great. I know the Fly team has an aversion to it but I really just wish they would hire some database folks and take on managed Postgres. I'm already running 8+ apps on there and it would be the peace of mind needed to move the rest across… one day.

Would love this also.

The best option I could find was using Digital Ocean Managed Databases. The cheapest costs $15, but you can host multiple databases with good insights and backups. You can choose where you host it, and place it close to the region where youre Fly.io apps are, with low latency.

Only caveat is there isn't an easy way to automatically update the IPs whitelist of the database, to support the Fly builder and deployed app(s).

Re: Migrating from AWS to Fly.io

#76

Post by subleq »

mrkurt wrote: post #69
tommoor wrote: post #59

Fly is great. I know the Fly team has an aversion to it but I really just wish they would hire some database folks and take on managed Postgres. I'm already running 8+ apps on there and it would be the peace of mind needed to move the rest across… one day.

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.

I'd trust a first-party managed postgres built by fly more than a third-party one.

Re: Migrating from AWS to Fly.io

#77

Post by rendaw »

mrkurt wrote: post #53
rendaw wrote: post #47

Earlier quoted context omitted.

I've been trying fly machines with terraform and running into one bug after another: https://github.com/fly-apps/terraform-provider-fly/issues/12... https://github.com/fly-apps/terraform-provider-fly/issues/12... https://github.com/fly-apps/terraform-provider-fly/issues/12... I was really excited since fly seems dead simple, but I haven't gotten it running yet...

The Terraform provider was a one off project from the community. We haven't really focused on it in earnest yet, unfortunately. We ended up sponsoring it, but until we get Fly apps off Nomad I don't think we'll have the best terraform story.

Sorry, not to use this as a support forum, but what exactly does it need? Just some provider-side bug fixes? Or are there Fly-side changes that need to be made before it will work? If it's something small I wouldn't mind poking at it.

Re: Migrating from AWS to Fly.io

#78

Post by Existenceblinks »

yodon wrote: post #66
mrdoops wrote: post #7

Earlier quoted context omitted.

The biggest $ cost I'd have on my radar WRT AWS vs Fly is complexity and need-to-know of employee time to do any given thing. Fly is way easier to navigate and use than AWS and its labyrinth of Cloud Scale™ horrors. The trade-off being you can do more given things with AWS.

>Fly is way easier to navigate and use than AWS and its labyrinth of Cloud Scale™ horrors Give fly.io a couple years and it will end up forced to take on all the complexity and edge cases AWS and Azure have to deal with today. A shiny new codebase is always nicer than an old one, because the old one has had to accommodate all those pesky customer needs.

You think it's inevitable? I think it's unlikely, they probably run into a different kind of targets. Those "edge cases" horror seem unnecessary like permission hell, pricing model hell (and too many size)

Re: Migrating from AWS to Fly.io

#79

Post by garganzol »

atonse wrote: post #70
tommoor wrote: post #59

Fly is great. I know the Fly team has an aversion to it but I really just wish they would hire some database folks and take on managed Postgres. I'm already running 8+ apps on there and it would be the peace of mind needed to move the rest across… one day.

The lack of “managed” Postgres is the only reason we haven’t moved 100% to fly. The idea of having to do my own upgrades by updating the docker container scares me. I have literally never run a stateful service off docker and don’t see the point, thanks to AWS. RDS has been extremely stable and boring. Maybe it’s out together by similar duct tape under the hood but it’s been incredibly solid for nearly a decade acros…

What stops you from using a managed database from a provider who specializes in it?

If Fly builds it, it will create another Goliath who tries to eat everything.

Re: Migrating from AWS to Fly.io

#80

Post by Existenceblinks »

mike_d wrote: post #10
l5870uoo9y wrote: post #2

> The main motivation to migrate was cost. Is Fly.io really than much cheaper for hosting CDN/Postgres/Docker Container?

I moved a service that was costing me $300+/mo to Fly and this month it was like $15. Some months I fall under the minimum $5 billing threshold and it is just free. They are the only provider that has nailed the killer feature: turn off shit while it isn't in use.

Yeah, I sometimes wonder if they bill me correctly. Their price is not that cheap but at the end of the day, the cost is lower than expected.
Post reply on HN