Isn’t Fly.io hosted on AWS (they don’t have their own hardware). Just like Heroku.
No, I don't think they are. The things they do with Anycast IPs I don't think is possible on AWS.
Migrating from AWS to Fly.io
31–40 of 189 posts
Re: Migrating from AWS to Fly.io
#32Earlier quoted context omitted.
https://fly.io/docs/postgres/ It isn't "Managed Postgres," but the differences are minimal. RDS is ultimately a solution for people who look in the mirror and confidently say "you don't know how to run a database."
> 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…
I look in the mirror and confidently say I don't know how to run a database. Was the grandparent comment meant to be an insult?
Re: Migrating from AWS to Fly.io
#33Re: Migrating from AWS to Fly.io
#34The article mentions this, but that’s strongly enough in my opinion. With fly you have no managed PostgreSQL. In my opinion, it’s not really comparable on cost to aws when Postgres is in the stack. You do read about interesting hacks where someone will set up rds in a region that may be single digit milliseconds away from a fly region. then, presumably, you could put PG bouncer on a sort of bastion host that connects…
https://fly.io/docs/postgres/ It isn't "Managed Postgres," but the differences are minimal. RDS is ultimately a solution for people who look in the mirror and confidently say "you don't know how to run a database."
What if I know how, and simultaneously don’t want to?
Re: Migrating from AWS to Fly.io
#35I moved a rails MVP from heroku to fly.io.
Biggest negative so far: no easy way to reset the database [1]. I'd typically like to blow it away and re-create it frequently as I tinker with it e.g. adding/removing/renaming a column or changing a data type. Those small changes now require migrations, which are a fair bit more work (but not a huge problem tbh).
Biggest positive: ability to select a zone meant response time for Australian users was very fast compared to heroku; making a big difference to UX.
Re: Migrating from AWS to Fly.io
#36I'm not sure this is well-known enough yet - fly now supports scale-to-zero services using fly machines - https://fly.io/docs/machines/
Does scale to zero work with ordinary fly apps yet?
Re: Migrating from AWS to Fly.io
#37I recently migrated some services from DigitalOcean to Fly and it was quite pleasant. My only issue is that routing to Fly from Southern California is awful. My friend and I have different ISPs and yet we’re both routed to the east coast instead of the much closer Los Angeles edge server. So our requests end up going to the east coast(edge), then back to the west coast (app), back to the east coast(edge), and then ba…
This is uncommon. When did it happen? We had some cross country routing issues a few weeks ago. We can generally fix these if you don't mind sending us traveroutes.
Here’s the forum thread I made about the issue. https://community.fly.io/t/how-is-edge-routing-determined/96...
Traces and ISP involved are in there. Thanks for looking into it!
Edit: I just double checked and it's still the same route to the east coast as posted in the thread
Re: Migrating from AWS to Fly.io
#38I recently migrated some services from DigitalOcean to Fly and it was quite pleasant. My only issue is that routing to Fly from Southern California is awful. My friend and I have different ISPs and yet we’re both routed to the east coast instead of the much closer Los Angeles edge server. So our requests end up going to the east coast(edge), then back to the west coast (app), back to the east coast(edge), and then ba…
What ISP's are involved here?
Cox and Spectrum. They route slightly different but both to the east coast. I linked the forum thread above.
Re: Migrating from AWS to Fly.io
#39Earlier 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…
I look in the mirror and confidently say I don't know how to run a database. Was the grandparent comment meant to be an insult?
I didn't interpreted as such but as an oversimplification and a sign of lack of operations experience as I stated at the beginning of my comment.
Re: Migrating from AWS to Fly.io
#40The article mentions this, but that’s strongly enough in my opinion. With fly you have no managed PostgreSQL. In my opinion, it’s not really comparable on cost to aws when Postgres is in the stack. You do read about interesting hacks where someone will set up rds in a region that may be single digit milliseconds away from a fly region. then, presumably, you could put PG bouncer on a sort of bastion host that connects…
https://fly.io/docs/postgres/ It isn't "Managed Postgres," but the differences are minimal. RDS is ultimately a solution for people who look in the mirror and confidently say "you don't know how to run a database."
> RDS is ultimately a solution for people who look in the mirror and confidently say "you don't know how to run a database."
In the same way that a RDBMS is ultimately a solution for people who look in the mirror and confidently say “you don’t know how to directly write to disc while guaranteeing the validity of relational data in spite of concurrent writes, power failures, etc.”