Following are the traditional methods of message transfer:-

• Message Queuing:- 
  A point-to-point technique is used in the message queuing pattern. A message in the queue will be destroyed once it has been consumed, similar to how a message is removed from the server once it has been delivered in the Post Office Protocol. Asynchronous messaging is possible with these queues.
  If a network problem delays a message's delivery, such as if a consumer is unavailable, the message will be held in the queue until it can be sent. This means that messages aren't always sent in the same order. Instead, they are given on a first-come, first-served BASIS, which can improve efficiency in some situations.

• Publisher - Subscriber Model:- 
  The publish-subscribe pattern entails publishers producing ("PUBLISHING") messages in multiple categories and subscribers consuming published messages from the VARIOUS categories to which they are subscribed. Unlike point-to-point TEXTING, a message is only removed once it has been consumed by all category subscribers.
  Kafka caters to a single consumer abstraction that encompasses both of the aforementioned- the consumer group. Following are the benefits of using Kafka over the traditional messaging transfer techniques:
  • Scalable: A cluster of devices is used to partition and streamline the data thereby, scaling up the storage capacity.
  • Faster: Thousands of clients can be served by a single Kafka broker as it can manage megabytes of reads and writes per second.
  • Durability and Fault-Tolerant: The data is kept persistent and tolerant to any hardware failures by copying the data in the clusters.