Scribd
Upload
14 views12 pages

Kafka Demo

Uploaded by

DummyBoy India
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
14 views12 pages

Kafka Demo

Uploaded by

DummyBoy India
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 12

KAFKA

A Brief Overview
AGENDA
 Messaging/Streaming Systems

 Broadcasting Model

 Pub Sub Model

 Systems Based on Pub Sub Model

 Kafka – An Introduction

 Topic in Kafka

 Partitions

 Producers and Consumers


MESSAGING/STREAMING
SYSTEMS

Onlin Offli
e ne
BROADCASTING MODEL
PUB SUB MODEL

Service
Provider 1

Service
Provider 2
SYSTEMS BASED ON PUB
SUB MODEL
KAFKA – AN
INTRODUCTION
Apache Kafka is an open-source distributed event streaming platform used by thousands
of companies for high-performance data pipelines, streaming analytics, data integration,
and mission-critical applications.
Kafka was created to address the data pipeline problem at LinkedIn. It was designed to
provide a high-performance messaging system that can handle many types of data and
provide clean, structured data about user activity and system metrics in real time
USPs
High Throughput
SCALABLE
PERMANENT STORAGE
HIGH AVAILABILITY
Cloud Native
Schema Support
TOPIC IN KAFKA
Messages in Kafka are categorized into topics.
The closest analogies for a topic are a database table or a folder in a filesystem.
A stream of events
Similar to Queue in other messaging systems
Topics in Kafka are always multi-producer and multi-subscriber
Events in a topic can be read as often as needed—unlike traditional messaging
systems, events are not deleted after consumption
PARTITIONS
 Topics are partitioned, meaning a topic is spread over a number of
"buckets" located on different Kafka brokers.
 This distributed placement of your data is very important for
scalability because it allows client applications to both read and
write the data from/to many brokers at the same time.
 When a new event is published to a topic, it is actually appended to
one of the topic's partitions.
PRODUCERS AND CONSUMERS
ConsumerGroup
Kafka Consumer-1

Topic
Partition-1

Producers
Producers Consumer-2
Producers Partition-2

Partition-3

Consumer-3
QUERIES

?
THANK
YOU

You might also like