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

11–20 of 189 posts

Re: Migrating from AWS to Fly.io

#11

Post by mike_d »

throwthere wrote: post #6

The 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."

Re: Migrating from AWS to Fly.io

#12

Post by jokethrowaway »

I found debugging setup errors on fly to be incredibly frustrating

You can't even ssh until the container started and they have some requirements on hostnames (0.0.0.0)

At least a few of their examples are broken.

The documentation could be better but it's pretty good

Is it better than Aws? Yes of course, you need to spend way more to get a dx as bad as Aws.

Setting up a VPS is a smoother experience than fly, though.

Once it's running, it's lovely and reminds me of heroku.

Re: Migrating from AWS to Fly.io

#13

Post by sosodev »

I 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 back to west coast (origin).

The latency adds up and makes requests to a nearby app almost as slow as to one hosted across an ocean.

I’m worried that other users will hit this and make hosting on Fly terrible for apps that require lower latency :/

Re: Migrating from AWS to Fly.io

#14

Post by [deleted] »

viraptor wrote: post #8

I missed when this was added: > if you configure your application to expose a Prometheus endpoint, those metrics will automatically show up on your Grafana dashboard But that's such an amazing and simple idea to integrate observability. Love the approach.

[deleted]

Re: Migrating from AWS to Fly.io

#15

Post by whalesalad »

sosodev wrote: post #13

I 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?

Re: Migrating from AWS to Fly.io

#16

Post by Octabrain »

mike_d wrote: post #11
throwthere wrote: post #6

The 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."

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). Between RDS and running a database on a virtual machine(s) and manage it with, let's say, Ansible for providing the four aforementioned features I would chose RDS any day of the week.

Re: Migrating from AWS to Fly.io

#17

Post by garganzol »

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.

This. We have a similar situation with Azure services being gradually migrated to Fly. Stuff that costed us $200+ to do on Azure is just like $15 on Fly.

Re: Migrating from AWS to Fly.io

#18

Post by fastball »

viraptor wrote: post #8

I missed when this was added: > if you configure your application to expose a Prometheus endpoint, those metrics will automatically show up on your Grafana dashboard But that's such an amazing and simple idea to integrate observability. Love the approach.

Isn't this just how Prometheus works alongside Grafana? I've never used fly.io but I've used that exact setup with these two services.

Re: Migrating from AWS to Fly.io

#19

Post by biorach »

jokethrowaway wrote: post #12

I found debugging setup errors on fly to be incredibly frustrating You can't even ssh until the container started and they have some requirements on hostnames (0.0.0.0) At least a few of their examples are broken. The documentation could be better but it's pretty good Is it better than Aws? Yes of course, you need to spend way more to get a dx as bad as Aws. Setting up a VPS is a smoother experience than fly, though.…

> You can't even ssh until the container started

In fairness, I'm struggling to think of a way they could get you to ssh to a container that hasn't started yet

> and they have some requirements on hostnames (0.0.0.0)

Can you clarify?

Re: Migrating from AWS to Fly.io

#20

Post by tptacek »

jokethrowaway wrote: post #12

I found debugging setup errors on fly to be incredibly frustrating You can't even ssh until the container started and they have some requirements on hostnames (0.0.0.0) At least a few of their examples are broken. The documentation could be better but it's pretty good Is it better than Aws? Yes of course, you need to spend way more to get a dx as bad as Aws. Setting up a VPS is a smoother experience than fly, though.…

Help me understand what you'd be SSH'ing into before your VM boots up? (I'm responsible for most of our SSH goop, so if there's an improvement to be made, I'm happy to make it).

A reminder: we don't run "containers". We take containers, unpack them, and transform them into VMs. There's no host OS for you to access.

Post reply on HN