Knowledge chain-Message middleware

Message middleware

Kafka

Kafka It is essentially a messaging system, unlike the traditional enterprise information queuing system, which deals with all data flowing through a company in near real-time, now serving LinkedIn, Netflix, Uber, and Verizon, and building a real-time information processing platform for this.

Application Scenarios:

1.Kafka can be applied to the message system, such as the more popular message push, these messages push the system's message source, you can use Kafka as the core of the system to complete the production of messages and message consumption.

2. The whereabouts of the website, we can be the Enterprise Portal, the user's operation records and other information sent to the Kafka, according to the actual business needs, can be real-time monitoring, or do offline processing.

3. Log collection, similar to the Flume suite, such as the log collection system, but the Kafka design architecture uses push/pull, suitable for heterogeneous clusters, Kafka can submit messages in bulk, for producer, in terms of performance is basically no consumption, and in the consumer side, We can use a distributed file storage system such as HDFS for storage.

Architecture principle: Kafka The preservation of messages is categorized according to topic, consisting of the message producer (Producer) and the message consumer (Consumer), and each server is called a broker. For Kafka clusters, both producer and consumer rely on zookeeper to ensure data consistency.

Kafka Combat-Getting Started

Kafka Combat-kafka Cluster

Kafka Combat-simple example

Knowledge chain-message middleware