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

121–130 of 189 posts

Re: Migrating from AWS to Fly.io

#121

Post by RussianCow »

funstuff007 wrote: post #44
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…

Isn't it usually a bad idea to have the database and application server in different data centers? It is / was my understanding that both the database and application server should ideally be on the same rack.

It's really just a matter of latency and bandwidth costs. If you can tolerate both, then keeping them in different data centers is fine. In fact, depending on your architecture, you may have to do this at some point anyway, even within the same cloud provider.

Re: Migrating from AWS to Fly.io

#124

Post by paulv »

Spivak wrote: post #85
garganzol wrote: post #79

Earlier quoted context omitted.

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.

Network posture? I can’t imagine trying to put the public internet in between my app servers and db.

Doesn't fly.io have tailscale integration?

Re: Migrating from AWS to Fly.io

#126

Post by yashap »

habibur wrote: post #61

Would have loved to read how much money they saved from this migration. The number's not there, unfortunately.

Author mentioned here that they went from $200/month on AWS to $90/month of Fly: https://news.ycombinator.com/item?id=34242923

Pretty tiny cloud costs either way, probably safe to assume they’re a small, early stage startup. But even still, it was likely a bad call to spend significant engineering effort on saving $110/month, which is a rounding error even for small startups. Hard to imagine that time couldn’t have been better spent on things that grow the business, like new features and bug fixes.

Re: Migrating from AWS to Fly.io

#127

Post by moltar »

lawnchair wrote: post #125

Author here. Some folks wanted the details on pricing. Pre migration, the Terrateam AWS monthly bill was about $200/mo. With Fly.io, we're paying around $90/mo.

Could you break down the costs of AWS?

From your post you say you needed a simple service plus a Postgres instance. I think you can have that for around $50 on AWS using a small EC2 and Aurora Serverless v2 (min $40/mo)

Re: Migrating from AWS to Fly.io

#128

Post by sausagefeet »

mrkurt wrote: post #51
mtlynch wrote: post #48

I've migrated several services from GCP to Fly.io, and I've been very happy with Fly. All of my apps are low-volume hobbyist web apps that run on a single machine, so I don't do any Terraform, k8s, or Postgres, so my use case is a little simpler than OP. My biggest complaint has been with outages,[0, 1, 2] but that's gotten better. The original architecture meant that larger servers could evict other users' running s…

You probably had a different community experience than recent folks. We've grown like 4x in the last 3 months and haven't kept up with community as well as I'd like (because hiring). And over holidays, we've had a difficult time with email support as well. It'll get better, but it's not great right now!

It's a breath of fresh air to see honesty about the good and bad from those at the company. Thank you for the transparency, I really appreciate it.

Re: Migrating from AWS to Fly.io

#129

Post by kitd »

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.

Openshift does something similar (though you need to annotate your deployments). But yes, the simplicity is refreshing.
Post reply on HN