Kafka is the Oracle of relays.
Discussion
I've never read any Kafka so I have no idea WTF this is supposed to mean.
Ah.
Ugh.
I'm not geeky enough for this.
It is not Franz it is Apache Kafka... Although Metamorphosis is a must in my opinion.
Why? Weird cockroach literature has never been on my list.
You will never see apples in the same way... I can't tell you more without spoiling it.
Oh, you can, because I'm likely never going to read it, there's way too many other books on my list that would take much more priority.
Here you go:
Gregor Samsa wakes up as a giant bug. His family, who he worked hard to support, turns on him. When his father throws apples at him (one getting stuck in his back) it shows how rejected and unwanted he’s become. Gregor is left to die alone, and his family is relieved to see him gone. The story’s a harsh look at how people are discarded when they’re no longer useful.
My son played the part of the jail orderly.
For messaging, I’ve always been a bigger fan of exactly-what-you-need via zeromq or nanomsg. Kafka is fine, and AWS makes it easy, but I find it’s often weirdly opinionated and sometimes limiting. And fucking expensive unless you’re self hosting.
We've got it running over 6 kubernetes nodes...
It's a monster.
Yep, that’s what I mean. As a thought experiment, consider how it could have been designed with direct peer to peer messaging via 0mq. You may have to do a bit of reading on it if you’re not familiar - it can seem like you’re having to build a lot from scratch. But it will only seem that way.
I’m curious if you might have found a lot of advantages this way.
The big issue you’ll run into is discoverability, but that’s easily managed by just updating a secrets list (or even just an s3 file) with the list of known listeners and producers.
I am currently running Apache Pulsar for the Noswhere indexer and it works pretty well.
That is also the basis of the event bus for NFDB relays, in non-persistent mode.
NFDB alone depends on 6 data stores, and has about 10 internal components
Sounds complicated until you try to store TBs of events cached all across the world, while maintaining high throughput, low cost, and supporting features like SmartCache and IA.
So yes, you can dump TBs of (public-domain) books into it, and it won’t care.
when a developer first explained nostr to me, I thought it seemed similar to Kafka
we should run nostr on kafka 😎
*looks at NFDB* hmm… I wonder what that is running (it’s something similar to Kafka but not exactly)