News for hackers. Stuff that matters.

toomanybits

Re:Scaling Kafka at Honeycomb on Wednesday December 01, 2021 @05:06AM (#29402352)
Now Kafka has ZK taken out and tiered storage coming in these factors are becoming mute points. With tiered storage Kafka has 2 layers and hence the benefits of broker/storage decoupling. By comparison, Pulsar has broker, bookkeeper, S3, and ZK layers to contend with. This is why a second layer was never added to Kafka directly.
Re:Kafka without ZooKeeper on Tuesday March 30, 2021 @06:13PM (#26641233)
I think that's one of the main points. Now you can run it as a single process more like a traditional broker (although it's obviously still a log).
Re:Pulsar vs. Kafka on Monday July 13, 2020 @06:57AM (#23819375)
I've heard of Comcast, but that's Yahoo. Not heard of the others.
Re:Pulsar vs. Kafka on Friday July 10, 2020 @11:00AM (#23792150)
Being used by at least one company of significant size that (a) i've heard of and (b) isn't directly connected to the project would be a good start.
Re:Pulsar vs. Kafka on Friday July 10, 2020 @10:44AM (#23791942)
You don't need a CS degree or Martin Kleppmann's book to work out it's a GPITA.
Re:Pulsar vs. Kafka on Friday July 10, 2020 @10:43AM (#23791921)
I'm lost too. Kafka auto creates topics by default. Maybe you're referring to being able to create more topics? But that seems to be unproven. Kafka's limit is metadata and Pulsar is more metadata dependent than Kafka.
Re:Pulsar vs. Kafka on Friday July 10, 2020 @10:40AM (#23791882)
> Pulsar will happily do with just 2x. This is just wrong. Pulsar provides weaker guarantees than Kafka. It's a quorum based system. If you run with two replicas Pulsar can't provide F-1 guarantees which Kafka can.
Re:Pulsar vs. Kafka on Friday July 10, 2020 @10:37AM (#23791860)
Nope. It sucks. RIP.
Re:Pulsar vs. Kafka on Friday July 10, 2020 @10:36AM (#23791849)
Show me one
Re:Pulsar vs. Kafka on Friday July 10, 2020 @10:35AM (#23791842)
1. is true, but if you want that data to move to a new node, it still needs to be replicated. Kafka's approach is to use tiered storage (which I believe is close to completion).

2. Kafka can read from a replica node. It's relatively new but it's there.

Re:Pulsar vs. Kafka on Friday July 10, 2020 @10:17AM (#23791680)
This smacks of being heavily one-product-focussed to me. Being a Kafka user it's hard enough managing and understanding one system, nevermind three or four joined together.

Maybe it's a bit faster or a bit more elastic, or whatever, who knows. What I really care about is whether I get called at 3am and in that regard the argument seems pretty weak. Kafka for all its woes is a solid system you know you can count on.

I'd much rather see someone come up with a truly innovative alternative that actually pushes the boundaries, rather than just copying what's there already, and adding a few window dressings.

Re:A EULA in FOSS clothing? on Monday December 17, 2018 @09:04AM (#18698950)
Are you sure? he seems to be using the past tense: "written so that software products like Landoop were free to embed our open source"
there's a live stream of this talk happening now https://www.youtube.com/watch?v=m-0cSdxiLLY#t=222