Towards Dev·4yKafka or RabbitMQ: What to Use When
Distributed messaging is based on the concept of reliable message queuing. Messages are queued asynchronously between client applications and messaging system. RabbitMQ is the ordinary queue management protocol (mainly using FIFO). Kafka also act as almost same but more than that we consider it as a stream processing system.
Dev Genius·4yKafka: Everything you need to know
Kafka offers much higher performance than message brokers like RabbitMQ. It uses sequential disk I/O to boost performance, making it a suitable option for implementing queues. It can achieve high throughput (millions of messages per second) with limited resources, a necessity for big data use cases.
Section·4yWhy Kafka is the Future of Messaging
Apache Kafka is a distributed, partitioned, replicated commit log service. It helps you process a large amount of data through the use of various Kafka consumers. It can be used as the central nervous system of a distributed architecture that delivers data to multiple systems. The primary reason behind developing Apache Kafka was to serve companies with fast and efficient data pipelines.
DZone·4yApache Kafka Patterns and Anti-Patterns
The Kafka Producer API sends data to topics in a Kafka cluster. It is possible that the producer application may end up sending the same message to Kafka more than once. The Producer API provides a simple way to avoid this by using the enable.idempotence property (which is set to false by default) Guidance on this topic will be covered later in this Refcard.