1)

Kafka is a circulated informing framework that we created for gathering and conveying high volumes
of log information with low dormancy. Kafka accomplishes a lot higher throughput than
traditional informing frameworks since they zeroed in on log handling applications thwy are
appropriate for both disconnected and online message utilization.
It consolidates the bar/sub worldview and highlight point conveyance. Merchants are utilized to course
messages from log servers to log shoppers. Messages or occasion logs are grouped into themes. Every
theme is additionally isolated into parcels to lessen mutex. A purchaser can prefer at least one themes.
At the point when the circulated side of the framework is concerned, the creators notice the idea of
customer gatherings – the objective is to partition the messages uniformly among the buyers. The
framework utilizes selective admittance to segments. The framework is decentralized, without an expert
hub and utilizing agreement administration Zookeeper. Kafka ensures essentially once conveyance as
the precisely once type would be pointless. At long last the creators present the utilization of the
framework at LinkedIn and propose two examinations, where they analyze the speed of devouring and
delivering of Kafka with two elective frameworks.

2)
It is Distributed and adaptable framework which offers high throughput. The API is like the informing
framework.
Straightforward Storage: Each parcel of a subject compares to a sensible log, and each log is carried
out as a bunch of portion records of the around a similar size. When there is another message from the
maker, the agent simply affixss it to the last fragment record. The logs get flushed after a configurable
number of messages set by the client. A message is simply presented to customers after it's flushed. No
message ID: each message is tended to by its intelligent offset in the log.

Effective exchange: Producer can present a bunch of messages in a solitary send demand. The
customer will get a few messages in a solicitation in any event, when they are handling the message
individually. No reserving: Relying on the record framework page store. Both maker and customer
access the portion records successively and the buyer frequently slacking the maker just barely. An API
"sendfile" is utilized to lessen superfluous 2 duplicates and 1 framework call.

Stateless Broker: How much every shopper has devoured isn't kept up with by the dealer, however by
the actual buyer. However, how to erase the message? Time sensitive SLA for maintenance strategy: A
message is naturally erased if it has been held in the agent longer than a specific period,

Pull model: They see as the "pull" model more reasonable for our applications since every purchaser
can recover the messages at the greatest rate it can maintain and try not to be overwhelmed by
messages pushed quicker than it can deal with. The force model additionally makes it simple to rewind
a purchaser. Kafka just assurances basically once conveyance. Conveyance ensures are frequently
needless excess for gathering log information. For example, losing a couple site visit occasions every
so often is surely not the apocalypse. On the off chance that an application thinks often about copies, it
should add its own de-duplication rationale, either utilizing the balances that we return to the shopper
or some exceptional key inside the message. This is normally a more financially savvy approach than
utilizing two-stage submits.

Kafka ensures that messages from a solitary segment are conveyed to a shopper all together.
Nonetheless, there is no assurance on the requesting of messages coming from various allotments.
3)
As per my research The pull based utilization model is definitely not a smart thought much of the time.
Pulling implies that the buyers need to continually checking for new messages in the merchants, which
brings about pointless data transmission utilization and pulling circles for the customers. Notice or
push component is more effective in scanty message climate.

There's no message handling in any structure, which implies that Kafka is just a slight layer between
message makers and customers.

Kafka has frail assurances as a dispersed informing framework. There's no requesting ensures when
the messages are coming from various segments. What's more, stateless agent implies that there's no
unshakable certainty on the message conveyance.

As Kafka use many techniques/methods for Distributed Messaging,which increases the complexity and
difficult to maintain.

I would you have made few changes to improve performance

An Effective monitoring tools would have been implemented to improve the Message transaction.

I would have worked to improve Performance and stability .

4)
Is there any other option to Improve monitoring tools which would Improve System Performance ?

How efficient Kafka will be when we have Redundant data ?

5)

Kafka is a disseminated informing framework that was produced for gathering and conveying high
volumes of log information with low idleness.

Below are links where I would see most of them have viewed this for there improvements in
developing/modifying new applications.

https://anantja.in/kafka/
https://medium.com/@vikashsahu4/kafka-a-distributed-messaging-system-for-log-processing-
ce62e396626c
https://xduan7.com/2016/04/05/paper-review-kafka-a-distributed-messaging-system-for-log-
processing/

https://data-flair.training/blogs/apache-kafka-tutorial/