What problem does it solve? Because latency is currently not an issue with all the regions from current cloud providers from my perspective. And for all static stuff you can use a CDN that has pop all arround the world / cities. Not sure I understand the use case of a single Docker image in a city outside of your entire backend services, especially the DB. If your Docker image talks to something else on AWS / GCP for…
They originally had (and seem to still have) the same JS runtime at the edge to give you a smart CDN/reverse proxy. They just updated it from being JS only to being able to run any Docker image. Cloudflare gives you a persistent key/value store and Fly provides a non-persistent Redis cache. You don’t have to move your entire app but there are plenty of use-cases where you can move more logic to the edge.
Launch HN: Fly.io (YC W20) – Deploy app servers close to your users
161–170 of 268 posts
Re: Launch HN: Fly.io (YC W20) – Deploy app servers close to your users
#162Congratulations on the launch! I've been following fly.io ever since I stumbled on it 2 years ago. A few questions, if I may: > We run a mesh Wireguard network for backhaul, so in flight data is encrypted all the way into a user application. This is the same kind of network infrastructure the good content delivery networks use. Does it mean the backhaul is private and not tunneling through the public internet? > fly.…
> Does it mean the backhaul is private and not tunneling through the public internet? Backhaul runs only through the encrypted tunnel. The Wireguard connection itself _can_ go over the public internet, but the data within the tunnel is encrypted and never exposed. > I use Cloudflare Workers and I find that at times they load-balance the traffic away from the nearest location [0][1] to some location half-way around th…
I'm guessing that's? https://github.com/geniousphp/autowire
Looks like it uses consul - is there a separate wireguard net for consul, or does consul run over the Internet directly?
Re: Launch HN: Fly.io (YC W20) – Deploy app servers close to your users
#163Does anyone know what did they use to build the docs? They look amazing. https://fly.io/docs/
We've gotten so many comments about the docs, I wish we could open source something but it's tightly coupled to other things that aren't useful to anyone else.
Re: Launch HN: Fly.io (YC W20) – Deploy app servers close to your users
#164Earlier quoted context omitted.
> Does it mean the backhaul is private and not tunneling through the public internet? Backhaul runs only through the encrypted tunnel. The Wireguard connection itself _can_ go over the public internet, but the data within the tunnel is encrypted and never exposed. > I use Cloudflare Workers and I find that at times they load-balance the traffic away from the nearest location [0][1] to some location half-way around th…
> Wireguard + backhaul were tricky (we use a tool called autowire to maintain wireguard settings across all the servers). I'm guessing that's? https://github.com/geniousphp/autowire Looks like it uses consul - is there a separate wireguard net for consul, or does consul run over the Internet directly?
Re: Launch HN: Fly.io (YC W20) – Deploy app servers close to your users
#165Do 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?
Re: Launch HN: Fly.io (YC W20) – Deploy app servers close to your users
#166Hi, this is a very cool product and I am planning a project that I think could use it. The question I have tho: How do you take advantage of the gains from this if you still need one master strictly consistent db for writes? Would a system design pattern to take advantage of fly.io be to have read only replicas on each geographic deploy or to only have region specific persistance? Apologies if this was already answer…
The "simplest" gains come from adding an in memory cache, we include Redis for this and some apps work really well just leaving the DB where it is, caching aggressively, and running close to users: https://fly.io/docs/redis/ Read only replicas are a great first step for most applications. I'd probably do caching first, then replicas (which are kind of like caching). Region specific persistence is one way to improve w…
Re: Launch HN: Fly.io (YC W20) – Deploy app servers close to your users
#167Do 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?
Re: Launch HN: Fly.io (YC W20) – Deploy app servers close to your users
#168If one API request makes on average 5-10 round trips to the database, and the database is in Virginia, this only makes the problem (much) worse. How do you solve this problem for this use case?
Re: Launch HN: Fly.io (YC W20) – Deploy app servers close to your users
#169So it’s google cloud run that scales to many servers?
(Cloud Run PM here) Cloud Run automatically scales your container image to thousands of container instances ("servers") if needed, maybe you mean "scales to many regions"?