Live data from Hacker News

Launch HN: Fly.io (YC W20) – Deploy app servers close to your users

news.ycombinator.com

11–20 of 268 posts

Re: Launch HN: Fly.io (YC W20) – Deploy app servers close to your users

#11
post #7

Honestly, while I'd love to try this out, I'm afraid of committing to a solution that might not be around long-term, which for me at least overrides concerns of peace of mind and ease of use, and I'm doing a hobby project at the moment. I'm using bare AWS at the moment because a) they gave me $5k in credits for YC SUS, b) they own the physical servers, and c) I can trust that they'll be around a long time, so I'd rat…

We're not AWS, but: 1) we own physical servers and 2) we're profitable 3) have big public companies as customers.

Re: Launch HN: Fly.io (YC W20) – Deploy app servers close to your users

#12

I like the idea of an edge service that is accessible to everyone. The list of cities looks pretty random to me. In particular I am not seeing anything in the Northeast, New York, etc. In upstate I already have 30ms latency to AWS and Azure in Ohio without terrible tail latency.

There's one in the Newark area: `ewr Parsippany, NJ (US)` from https://fly.io/docs/regions/

Thanks for pointing that out! That list is pretty disorganized... I made an issue to clean it up https://github.com/superfly/flyctl/issues/79

Re: Launch HN: Fly.io (YC W20) – Deploy app servers close to your users

#14

I like the idea of an edge service that is accessible to everyone. The list of cities looks pretty random to me. In particular I am not seeing anything in the Northeast, New York, etc. In upstate I already have 30ms latency to AWS and Azure in Ohio without terrible tail latency.

The city list does look random, but it's actually the simplest cities to build out with physical servers + anycast.

We _tend_ to do better than AWS on latency to your apps, and from upstate New York you'd probably be connecting to New Jersey. I would be Virginia is quicker than Ohio for you most of the time too.

Re: Launch HN: Fly.io (YC W20) – Deploy app servers close to your users

#15
post #13

Did y'all rack the servers that the containers run on? Or is it VMs running the containers? Just curious :)

We got someone else to rack them. Customer apps are VMs on top of the physical servers we lease. At scale we'll build our own datacenters, but at scale we can get not-me to do that.

Re: Launch HN: Fly.io (YC W20) – Deploy app servers close to your users

#16
post #11
post #7

Honestly, while I'd love to try this out, I'm afraid of committing to a solution that might not be around long-term, which for me at least overrides concerns of peace of mind and ease of use, and I'm doing a hobby project at the moment. I'm using bare AWS at the moment because a) they gave me $5k in credits for YC SUS, b) they own the physical servers, and c) I can trust that they'll be around a long time, so I'd rat…

We're not AWS, but: 1) we own physical servers and 2) we're profitable 3) have big public companies as customers.

Oh woah, profitable and own physical servers? You guys are gonna be just fine :)

Re: Launch HN: Fly.io (YC W20) – Deploy app servers close to your users

#17
post #14

I like the idea of an edge service that is accessible to everyone. The list of cities looks pretty random to me. In particular I am not seeing anything in the Northeast, New York, etc. In upstate I already have 30ms latency to AWS and Azure in Ohio without terrible tail latency.

The city list does look random, but it's actually the simplest cities to build out with physical servers + anycast. We _tend_ to do better than AWS on latency to your apps, and from upstate New York you'd probably be connecting to New Jersey. I would be Virginia is quicker than Ohio for you most of the time too.

I have timed Virginia and Ohio and Ohio is 20 ms faster.

I discovered this earlier when I was playing Titanfall and noticed a much lower ping to their Azure data center in Ohio. I confirmed it by setting up my own host in Azure.

I was thinking of switching to Azure but pretty soon AWS opened us-east-2 and I moved my stuff there.

Re: Launch HN: Fly.io (YC W20) – Deploy app servers close to your users

#18
post #11
post #7

Honestly, while I'd love to try this out, I'm afraid of committing to a solution that might not be around long-term, which for me at least overrides concerns of peace of mind and ease of use, and I'm doing a hobby project at the moment. I'm using bare AWS at the moment because a) they gave me $5k in credits for YC SUS, b) they own the physical servers, and c) I can trust that they'll be around a long time, so I'd rat…

We're not AWS, but: 1) we own physical servers and 2) we're profitable 3) have big public companies as customers.

Physical servers in Vultr right? I believe your geo regions are the same.

Re: Launch HN: Fly.io (YC W20) – Deploy app servers close to your users

#19
post #11
post #7

Honestly, while I'd love to try this out, I'm afraid of committing to a solution that might not be around long-term, which for me at least overrides concerns of peace of mind and ease of use, and I'm doing a hobby project at the moment. I'm using bare AWS at the moment because a) they gave me $5k in credits for YC SUS, b) they own the physical servers, and c) I can trust that they'll be around a long time, so I'd rat…

We're not AWS, but: 1) we own physical servers and 2) we're profitable 3) have big public companies as customers.

Congrats! I can see a lot of use cases for picking just a small subset of cities/regions and skipping Google/Amazon/Azure altogether.

Re: Launch HN: Fly.io (YC W20) – Deploy app servers close to your users

#20
post #18
post #11

Earlier quoted context omitted.

We're not AWS, but: 1) we own physical servers and 2) we're profitable 3) have big public companies as customers.

Physical servers in Vultr right? I believe your geo regions are the same.

So far only Packet, but we'll be expanding soon

edit: those regions are the same because it's the easiest set of cities to roll this out in :)

Post reply on HN