This means site activity (page views, searches, or other actions users may take) is published to central topics with one topic per activity type. The original use case for Kafka was to be able to rebuild a user activity tracking pipeline as a set of real-time publish-subscribe feeds. In this domain Kafka is comparable to traditional messaging systems such as ActiveMQ or In our experience messaging uses are often comparatively low-throughput, but may require low end-to-end latency and often depend on the strong Solution for large scale message processing applications.

In comparison to most messaging systems Kafka has better throughput, built-in partitioning, replication, and fault-tolerance which makes it a good

Message brokers are used for a variety of reasons (to decouple processing from data producers, to buffer unprocessed messages, etc). Kafka works well as a replacement for a more traditional message broker. Here is a description of a few of the popular use cases for Apache Kafka®.įor an overview of a number of these areas in action, see this blog post.

Sticky Previews 2.8 downloading