User Tools

Site Tools


products:ict:message_broker:apache_kafka

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
products:ict:message_broker:apache_kafka [2023/05/06 12:00] – created wikiadminproducts:ict:message_broker:apache_kafka [2023/05/06 12:01] (current) wikiadmin
Line 1: Line 1:
 +[[https://www.tutorialspoint.com/apache_kafka/apache_kafka_introduction.htm|
 +Apache Kafka - Introduction]]
 +
 +In Big Data, an enormous volume of data is used. Regarding data, we have two main challenges.The first challenge is how to collect large volume of data and the second challenge is to analyze the collected data. To overcome those challenges, you must need a messaging system.
 +
 +Kafka is designed for distributed high throughput systems. Kafka tends to work very well as a replacement for a more traditional message broker. In comparison to other messaging systems, Kafka has better throughput, built-in partitioning, replication and inherent fault-tolerance, which makes it a good fit for large-scale message processing applications.
 +
 +What is a Messaging System?
 +A Messaging System is responsible for transferring data from one application to another, so the applications can focus on data, but not worry about how to share it. Distributed messaging is based on the concept of reliable message queuing. Messages are queued asynchronously between client applications and messaging system. Two types of messaging patterns are available − one is point to point and the other is publish-subscribe (pub-sub) messaging system. Most of the messaging patterns follow pub-sub.
 +
 +
 [[https://www.redhat.com/architect/apache-kafka-java| [[https://www.redhat.com/architect/apache-kafka-java|
 Using Apache Kafka with Java: What architects need to know Using Apache Kafka with Java: What architects need to know
products/ict/message_broker/apache_kafka.1683356400.txt.gz · Last modified: 2023/05/06 12:00 by wikiadmin