Hacker News Reader

Comment by memset | Hacker News Reader

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?

View on HN

IPFS is slow and impractical. The design of the content addresssble system is cool, but having tried approximately annually to run it for production usage since it was released, I can say that it is still firmly in the “research project” category, a decade later.

The weakest part of IPFS in my experience is how long it takes one node to find another with the requested data across the internet through the public DHTs. I imagine it might work much better in this system if they're limiting it to only do lookups and fetches within your own network of nodes.

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

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.

Lately I've stumbled upon https://www.goqite.com/ but haven't had a good use case for it yet.

Reply on news.ycombinator.com