Live data from Hacker News

How Fly.io and Tailscale Saved Notado

notado.substack.com

31–40 of 112 posts

Re: How Fly.io and Tailscale Saved Notado

#31
I will migrate my tiny RDS and Cloud SQL side things to Fly.io a couple of weekends from now. It is definitely the sensible way for me to do this.

I managed my own SQL DB once upon a time and I can tell you I would rather have it done for me. 10 years on from when I set it up, my provider was going to get rid of the hardware and couldn't VM migrate me, so I took it down. No urge to manage this stuff myself.

Re: How Fly.io and Tailscale Saved Notado

#33

I'm curious as to why you chose to build your services in rust and then one microservice is in golang?

Thanks for this question!

Back in early 2020, Meilisearch did not have a Rust client library, but it did have a Go client library[1], and there was nothing comparable to lib/pq[1] in the Rust ecosystem which would allow me to create a listener on a table.[3]

Go is generally my "fallback language" when something would not be practical to do in Rust; it has a very nice, mature ecosystem, and as long as you aren't condemning yourself to interface{} hell, it remains in my eyes a perfectly capable and reasonably ergonomic alternative for well-defined use cases.

[1] https://github.com/meilisearch/meilisearch-go

[2] https://github.com/lib/pq

[3] https://pkg.go.dev/github.com/lib/pq#NewListener

Re: How Fly.io and Tailscale Saved Notado

#34
3000 users? You can save the data on disk and not worry about it. Get a vultr 5 dollar micro instance. I don't know why all these engineer driven businesses focus on the wrong things. You don't need fly.io. Of course they will tell you you need them, I don't blame them. But fly.io or kubernetes should always be done by a migration team which you can hire once you have insane profits. Yes profits, the other tiny detail most businesses are missing these days.

Re: How Fly.io and Tailscale Saved Notado

#35

3000 users? You can save the data on disk and not worry about it. Get a vultr 5 dollar micro instance. I don't know why all these engineer driven businesses focus on the wrong things. You don't need fly.io. Of course they will tell you you need them, I don't blame them. But fly.io or kubernetes should always be done by a migration team which you can hire once you have insane profits. Yes profits, the other tiny detai…

I won't tell you you need Fly.io. I am offended you'd put us in the same bucket as kubernetes though, rude.

Re: How Fly.io and Tailscale Saved Notado

#36
post #28

Earlier quoted context omitted.

They definitely are VPNs, just a specific subset of use cases of a VPN.

Semantically: those services are acting more like encrypted proxies, with some kind of exit far away from you physically. VPN's are usually used to create Virtual private networks . Extending your LAN across several sites using software, or granting you access to your LAN when you're not physically located close to it. It's hard to imagine why the meaning has changed as much as it has, because even though a consequen…

I see your point.

> encrypted proxies

I suggest "encrypted tunnels"

Re: How Fly.io and Tailscale Saved Notado

#37
post #33

I'm curious as to why you chose to build your services in rust and then one microservice is in golang?

Thanks for this question! Back in early 2020, Meilisearch did not have a Rust client library, but it did have a Go client library[1], and there was nothing comparable to lib/pq[1] in the Rust ecosystem which would allow me to create a listener on a table.[3] Go is generally my "fallback language" when something would not be practical to do in Rust; it has a very nice, mature ecosystem, and as long as you aren't conde…

Thank you for taking the time to answer, I'm always curious as to the why ;) Sounds like a good decision in that case! Good luck with your project!

Re: How Fly.io and Tailscale Saved Notado

#38
post #16

How is the latency and performance of Fly.io micro vms compared to, say, a comparably priced DigitalOcean VPS?

In the specific case of Notado, the Tailscale tunnel between Fly and Digital Ocean for database access naturally introduces some minimal additional latency. Besides this, I'm not sure I'm in the best position to compare the latency and performance of a service running 100% on a Digital Ocean VPS vs. a Fly.io micro VM. Hopefully someone else can chime in with their experiences on this thread.

I think that fly.io is still using firecracker for their microvm offering, although qemu has a similar machine type implemented.

Having worked on firecracker and with firecracker, it does a good job in the networking area.

Note that there's no multiqueue implementation available, so depending on how many connections and data you're passing through, it may start struggling if the workload is high.

I don't know the specifics of how DO sets up their VMs, but I assume that they're not doing any fancy networking optimizations, so you may end up with similar issues on both setups.

Re: How Fly.io and Tailscale Saved Notado

#39
post #28

Earlier quoted context omitted.

They definitely are VPNs, just a specific subset of use cases of a VPN.

Semantically: those services are acting more like encrypted proxies, with some kind of exit far away from you physically. VPN's are usually used to create Virtual private networks . Extending your LAN across several sites using software, or granting you access to your LAN when you're not physically located close to it. It's hard to imagine why the meaning has changed as much as it has, because even though a consequen…

In 2022, VPN is mostly about “getting around netflix geoblocking” or “getting around Chinese firewall”

Re: How Fly.io and Tailscale Saved Notado

#40
post #28

Earlier quoted context omitted.

They definitely are VPNs, just a specific subset of use cases of a VPN.

Semantically: those services are acting more like encrypted proxies, with some kind of exit far away from you physically. VPN's are usually used to create Virtual private networks . Extending your LAN across several sites using software, or granting you access to your LAN when you're not physically located close to it. It's hard to imagine why the meaning has changed as much as it has, because even though a consequen…

> It's hard to imagine why the meaning has changed as much as it has

Because the supporting infrastructure was historically called that, and it stuck. Just like how pocket computers are called "phones" because they evolved from telephones.

Post reply on HN