Live data from Hacker News

How Fly.io and Tailscale Saved Notado

notado.substack.com

91–100 of 112 posts

Re: How Fly.io and Tailscale Saved Notado

#91
post #28

Earlier quoted context omitted.

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.

And "Proxy" is already connected with other supporting infrastructure, so it's a bit hard to switch. FWIW I think I'll still try.

Re: How Fly.io and Tailscale Saved Notado

#92
post #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.

Haha, damn we need better one-liner analogies on these to easily discern the both in the future.

If k8s is ____, fly is ____.

I cant even compare fly to heroku, almost the same but different underneath.

Re: How Fly.io and Tailscale Saved Notado

#93
post #80

Earlier quoted context omitted.

FYI it’s cojones, not cajones. This is a typical misspelling. A cajón is a wooden drawer or box. A cojón is the singular of cojones.

Maybe they covet ilrwbwrkhv's worldly possessions, due to their financial success stemming from their ability to reliably write files to local storage devices.

Real wood, none of that glued together reconstituted shit regular peasant devs use.

Re: How Fly.io and Tailscale Saved Notado

#94
post #81

Earlier quoted context omitted.

Even if it would be best for the company, "managing VMs" is less impressive on a resume than "set up auto-scaling and server IAM utilizing fly.io and Tailscale".

I’m not sure resume-driven development is a trend we should embrace. (Even if we all acknowledge that it is one motivation for many tech fads). Honestly, if this is on a resume the next question should be — tell me why you needed such a system…

That's why I advocate for MDD instead, short for Magpie Driven Development.

Just as Magpies like their shiny trinkets, I like my shiny frameworks.

Re: How Fly.io and Tailscale Saved Notado

#95
post #59
post #47

Earlier quoted context omitted.

> You can save the data on disk and not worry about it. I one day aspire to have the cajones of ilrwbwrkhv. For the reference of other potential solo devs, if done right, Fly.io will still be cheaper than the Vultr 5 dollar micro instance (or equivalent) with an incomparably better DX.

With the threat of a much higher bill if done wrong. That $2.50 vultr instance provides a lot more like 20 gigs of storage nevermind security of a fixed bill. You might be able to save a little, you might pay a lot more. Hedge your bet and use vultr.

It's just as if "running a single container hands-off" and "having 1-n VPS" can be completely different things for different use cases.

Re: How Fly.io and Tailscale Saved Notado

#96

Earlier quoted context omitted.

Uh huh here we go. What other tool do you propose for running many containers with dependencies on one another? Or why should I target a bunch of different cloud APIs to make my tool consumable when I can target one?

First question: why you need many containers for just 3000 users? That should easily run on a cheap VPS unless you're doing something ridiculously complex. Why target any cloud APIs at all if your product have a small amount of users? You don't need to scale up/down fast at if you're just at 3000 users. Throw it on a Linux box, write a systemd service and be done with it.

I'm not talking about 3k users, he said 99% of use cases

Re: How Fly.io and Tailscale Saved Notado

#97
post #79

Earlier quoted context omitted.

Uh huh here we go. What other tool do you propose for running many containers with dependencies on one another? Or why should I target a bunch of different cloud APIs to make my tool consumable when I can target one?

Nomad is pretty fantastic!

Yeah nomad is okay but not as functional as k8s (yet)

Re: How Fly.io and Tailscale Saved Notado

#98

Earlier quoted context omitted.

First question: why you need many containers for just 3000 users? That should easily run on a cheap VPS unless you're doing something ridiculously complex. Why target any cloud APIs at all if your product have a small amount of users? You don't need to scale up/down fast at if you're just at 3000 users. Throw it on a Linux box, write a systemd service and be done with it.

I'm not talking about 3k users, he said 99% of use cases

> 99% of companies

Most companies have small amount of users and don't have rapidly shrinking/growing user bases, meaning their infrastructure need is not rapidly shrinking/growing neither, in most cases.

Hence, Kubernetes being accidental complexity most people can do without, rather than necessary complexity.

Re: How Fly.io and Tailscale Saved Notado

#99
post #79

Earlier quoted context omitted.

Nomad is pretty fantastic!

Yeah nomad is okay but not as functional as k8s (yet)

What are you able to do in Kubernetes that you cannot (yet) do in Nomad? Seems to cover exactly the same use cases, and more even, as you can run non-containers in Nomad and also Nomad seems to require less resources for hosts so you could run it on much smaller devices/instances.

Re: How Fly.io and Tailscale Saved Notado

#100
post #80

Earlier quoted context omitted.

FYI it’s cojones, not cajones. This is a typical misspelling. A cajón is a wooden drawer or box. A cojón is the singular of cojones.

Maybe they covet ilrwbwrkhv's worldly possessions, due to their financial success stemming from their ability to reliably write files to local storage devices.

My favourite comment on this post. Thanks both to you for this great joke and to the parent commenter for the correction!
Post reply on HN