Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

github.com

Post reply on HN
Print view View original

121–130 of 149 posts

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#121

Post by gedw99 »

memset wrote: post #11

This is really neat! I'm working a message queue in go (drop-in replacement for SQS) and also thinking about autoscaling. I've been playing with raft vs using a central store (ie, postgres) to coordinate. Can you tell me more about IPFS - I've never used it before. How has that been working, and can you tell me what you've observed when you have many nodes which need to coordinate?

I am using nats Jetstream with nex.

It’s a self hosted Cloudflare.

It uses nats Jetstream , as a work around to Nat having bog / anycast , like how Cloudflare does its magic.

https://github.com/synadia-io/nex

You have to run it on bare metal or any cloud that supports next virtualisation.

I use nats Jetstream listening to git repo web hooks to deploy.

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#122

Post by dsamy »

hosh wrote: post #4

There are some neat ideas here -- building a PAAS off of p2p technologies to enable network autodiscovery, automated load-balancing, distributed storage, Webassembly-native, etc. Having put stuff through production though, I'm a bit skeptical about how well it works out in the wild, though I am interested in learning how well it does and what its failure modes are. If it works well-enough, it has the potential for de…

Scaling using p2p is something that some of the big Silicon Valley giants use internally. It scales very well. Tau uses a combination of techniques on top of the DHT to ensure response time is quick. Unfortunately, our documentation is not that great (working on it), but we have three services that accelerate discovery and routing: Seer (keeps tabs on nodes' health and offers a DNS interface as well), Gateway (a load balancer that forwards traffic to nodes it keeps tunnels with), and TNS (a replicated registry of resources: what is what).

Between Seer and Gateway, the system handles resiliency. Internally, CRDT is used for replication, which: * allows nodes to still work offline or if the network gets partitioned * prevents split-brain

The cons of CRDT are when it comes to orchestrating services like databases; we could end up with multiple instances of a master node, for example. This is why we plan to add a cluster mechanism that will allow the formation of dynamic clusters to facilitate the orchestration of stateful containers and VMs.

For the money part, we have a managed offering, enterprise support, a web console, and are building more.

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#123

Post by dsamy »

bitpush wrote: post #3

First coolify[1] and now Tau. More competition the better for users. From the quick look it seems like coolify is more fully featured? [1]: https://coolify.io/

It's a different approach. Coolify is a container management platform with CI/CD integration. Tau is meant for developers, and Git is the only way to make changes. Moreover, Tau can handle compute, storage, pub-sub, and more. Note that, besides CI/CD, Tau cannot orchestrate containers currently.

So, being fully featured truly depends on your intended use case.

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#124

Post by dsamy »

TechDebtDevin wrote: post #7
bitpush wrote: post #3

First coolify[1] and now Tau. More competition the better for users. From the quick look it seems like coolify is more fully featured? [1]: https://coolify.io/

Coolify needs a lot of work imho.

Especially when scaling beyond one server. The next Tau release will include `spore-drive`, a tool for deploying and updating on thousands of servers with a single command.

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#125

Post by dsamy »

turtlebits wrote: post #28

Looks compelling, but the docs are extremely vague and full of fluff. The "Why One Binary" is hilariously bad. Almost feels like content to impress managers/recruiters. https://tau.how/02-concepts/03-one-binary/#the-genesis-of-ta...

sorry about that. it's true our doc is so so... we're working on it.

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#127

Post by dsamy »

slillibri wrote: post #112

If it’s a single binary why is there an installer, and why does it need to be curl-piped to sh? Looking at the installer script, why does it create directories in the root dir, instead of /opt or /usr/local? Also, I couldn’t find the install script in the linked repo.

the script downloads the latest release. it's still one binary you can deploy yourself or compile with `go build`. the script is really there to automate some steps. next release a new tool `spore-drive` will allow to deploy all your nodes running one command.

for the `/tb` folder, I see your point, i would love to discuss it further if you can open an issue on github.

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#128

Post by dsamy »

memset wrote: post #11

This is really neat! I'm working a message queue in go (drop-in replacement for SQS) and also thinking about autoscaling. I've been playing with raft vs using a central store (ie, postgres) to coordinate. Can you tell me more about IPFS - I've never used it before. How has that been working, and can you tell me what you've observed when you have many nodes which need to coordinate?

we don`t use a full IPFS, but more like a lite version. it allow us to retrieve data quickly, cache and duplicate. check this article https://blog.ipfs.tech/2020-02-14-improved-bitswap-for-conta...

When it comes to scale, ipfs basic discovery mechanism (the dht) does not do that well. This is why we have services like tns (which is a replicated registry) that allows it to scale.

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#129

Post by dsamy »

gedw99 wrote: post #121
memset wrote: post #11

This is really neat! I'm working a message queue in go (drop-in replacement for SQS) and also thinking about autoscaling. I've been playing with raft vs using a central store (ie, postgres) to coordinate. Can you tell me more about IPFS - I've never used it before. How has that been working, and can you tell me what you've observed when you have many nodes which need to coordinate?

I am using nats Jetstream with nex. It’s a self hosted Cloudflare. It uses nats Jetstream , as a work around to Nat having bog / anycast , like how Cloudflare does its magic. https://github.com/synadia-io/nex You have to run it on bare metal or any cloud that supports next virtualisation. I use nats Jetstream listening to git repo web hooks to deploy.

love NATS. tau is about the developer experience and speed of development. Integrating and maintaining nex is not something every dev can do

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#130

Post by dsamy »

VyseofArcadia wrote: post #21

I've been out of web dev for a few years, but my understanding of the appeal of serverless is that it is theoretically pay only for what you use. But if you're hosting Tau to do serverless via Tau, well, it's not really serverless anymore. You are now definitely paying for the server running the serverless infra. Why would anyone target Tau serverless, then? What am I missing?

as cal85 said, The appeal of serverless for me is simplicity. that said, tau will support containers and even VMs by the end of the year
Post reply on HN