Zookeeper:

basic

distributed-system-using-zookeeper-and-java

https://zookeeper.apache.org/doc/current/zookeeperStarted.html#sc_Prerequisites

https://zookeeper.apache.org/doc/current/zookeeperProgrammers.html#ch_programStructureWithExample

https://www.youtube.com/watch?v=2RfBHqDWa60

• how-to-do-distributed-locking https://martin.kleppmann.com/2016/02/08/how-to-do-distributed-locking.html

-Zookeeper for distributed key value store design

---

#Kafka :

Video Tutorial for kafka

RabbitMQ vs. Kafka vs. ActiveMQ

Here are the top differences between RabbitMQ, Kafka, and ActiveMQ:

Performance and Scalability: Kafka is designed for high throughput and horizontal scalability, making it well-suited for handling large volumes of data. RabbitMQ and ActiveMQ both offer high performance, but Kafka generally outperforms them in terms of throughput, particularly in scenarios with high data volume.

Message Ordering: RabbitMQ and ActiveMQ guarantee message ordering within a single queue or topic, respectively. Kafka ensures message ordering within a partition but not across partitions within a topic.

Message Priority: RabbitMQ and ActiveMQ support message prioritization, allowing messages with higher priority to be processed before those with lower priority. Kafka does not have built-in message priority support.

Message Model: RabbitMQ uses a queue-based message model following the Advanced Message Queuing Protocol (AMQP), while Kafka utilizes a distributed log-based model. ActiveMQ is built on the Java Message Service (JMS) standard and also uses a queue-based message model.

Durability: All three message brokers support durable messaging, ensuring that messages are not lost in case of failures. However, the mechanisms for achieving durability differ among the three, with RabbitMQ and ActiveMQ offering configurable durability options and Kafka providing built-in durability through log replication.

Message Routing: RabbitMQ provides advanced message routing capabilities through exchanges and bindings, while ActiveMQ uses selectors and topics for more advanced routing. Kafka's message routing is relatively basic and relies on topic-based partitioning.

Replication: RabbitMQ supports replication through Mirrored Queues, while Kafka features built-in partition replication. ActiveMQ uses a Master-Slave replication mechanism.

Stream Processing: Kafka provides native stream processing capabilities through Kafka Streams, similarly RabbitMQ offers stream processing too, while ActiveMQ relies on third-party libraries for stream processing.

Latency: RabbitMQ is designed for low-latency messaging, making it suitable for use cases requiring near-real-time processing.

License: RabbitMQ is licensed under the Mozilla Public License, while both Kafka and ActiveMQ are licensed under the Apache 2.0 License.