Live data from Hacker News

How Fly.io and Tailscale Saved Notado

notado.substack.com

101–110 of 112 posts

Re: How Fly.io and Tailscale Saved Notado

#101
post #82

Earlier quoted context omitted.

You can save the data on disk and not worry about it. Like in sqlite or something like json files?

Filesystems have a lot more flexibility than just storing JSON or databases. A notes app probably should just store markdown files with some links between each other, and a few small databases for indexes.

You could also store base64 encoded blobs in yaml, or implement a self-modifying bash script key-value store you call into from a shell. Those are the only other options before it's time to move everything over to into the cloud.

Re: How Fly.io and Tailscale Saved Notado

#102

Earlier quoted context omitted.

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.

Well for one, you need to pair nomad with consul and vault just to get remotely close. Then you are missing all the packages purpose built for k8s, the extensibility of k8s, and Nomad is built by a for profit company while k8s is purely OSS

Re: How Fly.io and Tailscale Saved Notado

#103

Earlier quoted context omitted.

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.

Eh I don't have the numbers, but every company I've worked for has had lots of users. Their infra wasn't shrinking or growing much to make good use of k8s. Mainly they needed to link a bunch of runtime containers together built by different teams.

I get why people say k8s is complex, but there really isn't another great option for running a containerized service based architecture, maybe nomad

Re: How Fly.io and Tailscale Saved Notado

#104
post #52

Quoted post unavailable.

Nobody's sponsoring anything or "folding" anything on HN. We only care what users find interesting.

The interest in fly.io, and the few other startups people get excited about, is definitely organic. I wish there were more of them—it would be good for the community and therefore for the forum.

Re: How Fly.io and Tailscale Saved Notado

#105
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.

> Just like how pocket computers are called "phones"

Yeah, that's a really good point.

I guess at least we have the modifier "mobile" and "smart" to differentiate the different types of phone (up to and including the pocket computer).

I don't think there is a written equivalent of a VPN which is only acting as an exit node.

Re: How Fly.io and Tailscale Saved Notado

#106

Earlier quoted context omitted.

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.

Well for one, you need to pair nomad with consul and vault just to get remotely close. Then you are missing all the packages purpose built for k8s, the extensibility of k8s, and Nomad is built by a for profit company while k8s is purely OSS

Yeah, guess Nomad plays a bit more the role of "do one thing well" rather than "everything in a box" approach that Kubernetes has. And for sure, Kubernetes ecosystem is a bit wider than Nomad at the moment.

But again, what specifically are you able to do in Kubernetes that you cannot do in Nomad? You mentioned it's not as "functional" but seems you're unable to actually specify what you mean by this.

> Nomad is built by a for profit company while k8s is purely OSS

Not sure how you can claim Kubernetes somehow is "more OSS" than Nomad? Both are under FOSS licenses (Nomad: MPL, Kubernetes: Apache) but both are mainly maintained by two big for-profit companies (Nomad: HashiCorp, Kubernetes: Google). They are both the same in this regard, both are the "same amount of OSS", whatever that means.

Re: How Fly.io and Tailscale Saved Notado

#107
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…

I see your point. > encrypted proxies I suggest "encrypted tunnels"

Perhaps something like...stunnel...released in 2000-ish?

Re: How Fly.io and Tailscale Saved Notado

#108
post #8

Earlier quoted context omitted.

Man, marketing of those tunneling services as VPNs is actually causing damage. Those services are NOT VPNs. Tailscale is very much more like a real VPN than those other things that are pretending to be VPNs.

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

One could possibly apply the VPN label because you go through layers of connections on a private network to go back onto the internet. I did a cursory search of the TOR website and can't find anything labeling it a VPN. But that is one of the big projects that kinda started all of this.

In fact, TOR describes an overlay network, and that's how projects like Nebula also describe their functionality. Granted, Nebula is more like a VPN than "VPN providers" also.

"VPN providers" provide a service for accessing the public internet as proxies, tunnels, etc, for evading region blocks, getting around privacy destroying things, and all that stuff. I won't knock their value. I've use them when needing internet over an open WIFI access point. I'm generally not involved in activist activities nor otherwise in harms way, so I don't have much else use of them.

But I do have use of a virtual private network. As in the core idea of it. I have a private network at home. It's not publicly available. I use Tailscale, currently, to access it when not connected directly to my home network (as in, not at home). My portable device becomes a member of a private network that has access to my private home network. This is a VPN.

I really think VPN was (incorrectly) chosen for secured proxy services because it's a simple and familiar name. The marketing using the terms "virtual private network" came far later to describe a way to secure your privacy. But it's diluted the actual technical term.

Re: How Fly.io and Tailscale Saved Notado

#109

Earlier quoted context omitted.

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.

Well for one, you need to pair nomad with consul and vault just to get remotely close. Then you are missing all the packages purpose built for k8s, the extensibility of k8s, and Nomad is built by a for profit company while k8s is purely OSS

Just to note: Nomad has added service discovery (https://www.hashicorp.com/blog/nomad-1-3-adds-native-service...) and a secrets system (https://www.hashicorp.com/blog/nomad-1-4-adds-nomad-variable...) in the past few months. You can run Nomad without Consul or Vault for many use-cases now.

Re: How Fly.io and Tailscale Saved Notado

#110

Earlier quoted context omitted.

Well for one, you need to pair nomad with consul and vault just to get remotely close. Then you are missing all the packages purpose built for k8s, the extensibility of k8s, and Nomad is built by a for profit company while k8s is purely OSS

Yeah, guess Nomad plays a bit more the role of "do one thing well" rather than "everything in a box" approach that Kubernetes has. And for sure, Kubernetes ecosystem is a bit wider than Nomad at the moment. But again, what specifically are you able to do in Kubernetes that you cannot do in Nomad? You mentioned it's not as "functional" but seems you're unable to actually specify what you mean by this. > Nomad is built…

> but both are mainly maintained by two big for-profit companies (Nomad: HashiCorp, Kubernetes: Google

This is deeply untrue of Kube, it's maintained by lots of companies, and is in a totally separate organization than Google with distinctly different governance. Kube goes out of its way to ensure its not dominated by one organization and has stats on this. I haven't looked at the Nomad stats but I imagine its nowhere near that and still under the Hashicorp umbrella and pretty much only works with Hashicorp stuff.

> But again, what specifically are you able to do in Kubernetes that you cannot do in Nomad?

The big thing for me is API extensibility. The Kube CRD is one of the more powerful abstractions to hit infrastructure in awhile. The ability to create your own controllers and offer consistent APIs to an end user is imperfect but incredibly useful.

Other thoughts:

* Kube is supported by every major cloud provider.

* I'm not a fan of HCL, some people like it but I prefer Kube's approach of decoupling the templating from the core app.

Post reply on HN