How does this compare to Redis Pub-Sub or RabbitMQ?
This scales to multi-datacenter deployments well. Has strong multi-tenancy support if memory serves Yahoo is running a single cluster for all of their properties.
Apache Pulsar is an open-source distributed pub-sub messaging system
11–20 of 249 posts
Re: Apache Pulsar is an open-source distributed pub-sub messaging system
#12How does this compare with NATS?
Re: Apache Pulsar is an open-source distributed pub-sub messaging system
#13Re: Apache Pulsar is an open-source distributed pub-sub messaging system
#14How is it compared to kafka?
Re: Apache Pulsar is an open-source distributed pub-sub messaging system
#15How does this compare to Redis Pub-Sub or RabbitMQ?
It's a persistent store, so that would be different from Redis Pub-Sub. Compared to RabbitMQ, Pulsar seems to favor strong ordering and protection from message loss.
This blog post offers some more info and leaders to other posts comparing Pulsar to RabbitMQ and Kafka: https://jack-vanlightly.com/blog/2018/10/2/understanding-how...
Re: Apache Pulsar is an open-source distributed pub-sub messaging system
#16How is it compared to kafka?
Most of the flaws of Kafka are carefully studied and fixed in Apache pulsar. I have written a blog about why we went ahead with pulsar https://medium.com/@yuvarajl/why-nutanix-beam-went-ahead-wit...
Re: Apache Pulsar is an open-source distributed pub-sub messaging system
#17For a moment I thought Bajaj and TVS came together.
Captain here.
TVS and Bajaj are major motorbike manufacturers in India, and TVS had a model named "Apache" and Bajaj had a model named "Pulsar".
Flies away
Re: Apache Pulsar is an open-source distributed pub-sub messaging system
#18Sidenote question :
Are we heading toward a split between apache/java/zookeeper stacks and go/etcd on the other ? I've seen an issue related to that question on pulsar, and this got me investigating the distributed KV part of the stack.
It seems by looking at some benchmark that etcd is much more performant than zookeeper, and that to some people, operating two stacks seems like an operation maintenance cost a bit too high. Is that a valid concern ?
Also, i've seen that kafka is working on removing the dependency to zookeeper, is pulsar going to take the same road ?
Re: Apache Pulsar is an open-source distributed pub-sub messaging system
#19"high-level APIs for Java, C++, Python and GO", no love for Node.js? :(
It exists: https://pulsar.apache.org/docs/en/next/client-libraries-node...
However it currently lacks the ability to listen for messages and run an event handler when one comes in: https://github.com/apache/pulsar-client-node/pull/56
You have to manually call ".receive()" to attempt to receive a message.
Re: Apache Pulsar is an open-source distributed pub-sub messaging system
#20Sidenote question : Are we heading toward a split between apache/java/zookeeper stacks and go/etcd on the other ? I've seen an issue related to that question on pulsar, and this got me investigating the distributed KV part of the stack. It seems by looking at some benchmark that etcd is much more performant than zookeeper, and that to some people, operating two stacks seems like an operation maintenance cost a bit to…
> is pulsar going to take the same road ?
Yes, it's in the works