Live data from Hacker News

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

news.ycombinator.com

191–200 of 268 posts

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

#191
post #107

Earlier quoted context omitted.

I don't think I like the failure mode of your app getting slower (losing your ApplicationDN) right at the time it's really popular. I don't have a better solution though.

> I don't have a better solution though Don't host in such a way that you're paying for traffic... Hetzner, OVH and Packet all have dedicated servers where you don't pay for the traffic, inbound or outbound. Edit: judging by other comments here, it might seem like US zone of Fly.io is in fact hosted in Packet so they are probably themselves not paying for the traffic. Maybe they are using Hetzner for the EU zone (or…

Packet charges for outbound bandwidth. The places you can get close to free on outbound bandwidth don’t give you the ability to do anycast and tend to over subscribe their networks.

We’d like to grt network prices down but we can’t run our service on ovh or Hetzner.

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

#193

Earlier quoted context omitted.

Why would I care? I have That's not meant to be a snarky question, I genuinely don't understand what business problem that's going to be solved by saving at most 30 ms. Anything written in Rails/Django, talking to a DB, etc. is going to have request latency dominated by other parts of the stack.

We have some benchmarks comparing us to Heroku (on AWS) and the performance gains from faster networking alone are nothing to sneeze at: https://fly.io/blog/turboku/

If the value prop is that you're Heroku, but faster, I can understand that.

I think it's misleading to say that deficiencies of Heroku have anything do to with AWS though. It's really, really easy to set up anycast [https://aws.amazon.com/global-accelerator/] with ECS [especially if you're willing to pay for Fargate]. If your product does something meaningfully different than that, I'd love to know more.

NB: I'm in no way affiliated with AWS or Heroku, just have experience with both in the past.

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

#194
post #181

Have been building a similar project in the past few months called Valar ( https://valar.dev , it uses gVisor instead of Firecracker and is still in private beta), but I prioritized university studies so it took too much of my time to actually release it publicly. Great to see a similar product being released, really looking forward to test it. Best of luck to you!

How are you liking gVisor? We started with Firecracker and only spent a little time with gVisor, but it seems really nice.

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

#195
post #69

Do you guys plan to add an offering for a distributed database that we could match with this compute? That way we could build entire application on edge without buying into the FaaS movement.

> That way we could build entire application on edge without buying into the FaaS movement So you want to be able to upload your code and have someone manage the infrastructure and datastore. Isn't that the definition of FaaS?

That sounds like the definition of “utopia” to me.

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

#196
Well I just signed up and tested one of my Heroku apps, got it working with just a few clicks, really impressive. Are there any way to see stats like memory usage? What happens if an app goes over the limit? (heroku has some swap space before it kills an app, and then I can see it in the logs)

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

#197
post #107

> 2. Max monthly spend: unexpected traffic spikes happen, and the thought of spending an unbounded amount of money in a month is really uncomfortable. You can configure fly.io apps with a max monthly budget, we'll suspend them when they hit that budget, and then re-enable them at the beginning of the next month. I like this, not having caps is a major problem with some of your competition for smaller projects/compani…

I don't think I like the failure mode of your app getting slower (losing your ApplicationDN) right at the time it's really popular. I don't have a better solution though.

Unless your popularity pays your bills, it's the most graceful degradation you can have.

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

#198

Well I just signed up and tested one of my Heroku apps, got it working with just a few clicks, really impressive. Are there any way to see stats like memory usage? What happens if an app goes over the limit? (heroku has some swap space before it kills an app, and then I can see it in the logs)

That's great to hear! Apps are allowed to burst over the limit if the host has free resources. We don't offer much visibility into metrics yet but we're working on it. All our metrics are going into prometheus with some awesome dashboards in grafana that we can't wait to expose to customers.

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

#199
post #107

Earlier quoted context omitted.

I don't think I like the failure mode of your app getting slower (losing your ApplicationDN) right at the time it's really popular. I don't have a better solution though.

maybe if you go over, you automatically add ads to the page or something.

A "donate" button when the current remaining budget would last for less than 100 minutes.

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

#200

Fly.io is the service I’ve been most excited to see make headway in a long time. Pairing this with a global sql ( cough cockroach cough*) is literally the app platform I’ve been dreaming about. I would like to see more documentation around push based architectures. That is I want to build a system where a process pushes to the Redis in fly but is not running itself in fly. Basically something that may be unrouteable…

Thanks for the kind words! Cockroach is awesome and it's something we'd like to offer someday. Until then checkout FaunaDB.

Your push example is interesting. We don't have a way to connect to redis from outside fly, but you could certainly boot up a tiny app on fly that acts as a proxy from external apps into the fly redis.

Post reply on HN