Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Kafka
Kafka

4.7K
4.2K
+ 1
484
Kafka Streams
Kafka Streams

80
75
+ 1
0
Add tool

Kafka vs Kafka Streams: What are the differences?

Kafka: Distributed, fault tolerant, high throughput pub-sub messaging system. Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design; Kafka Streams: A client library for building applications and microservices. It is a client library for building applications and microservices, where the input and output data are stored in Kafka clusters. It combines the simplicity of writing and deploying standard Java and Scala applications on the client side with the benefits of Kafka's server-side cluster technology.

Kafka and Kafka Streams are primarily classified as "Message Queue" and "Stream Processing" tools respectively.

Kafka is an open source tool with 13.1K GitHub stars and 6.99K GitHub forks. Here's a link to Kafka's open source repository on GitHub.

According to the StackShare community, Kafka has a broader approval, being mentioned in 691 company stacks & 2401 developers stacks; compared to Kafka Streams, which is listed in 7 company stacks and 5 developer stacks.

No Stats
- No public GitHub repository available -

What is Kafka?

Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.

What is Kafka Streams?

It is a client library for building applications and microservices, where the input and output data are stored in Kafka clusters. It combines the simplicity of writing and deploying standard Java and Scala applications on the client side with the benefits of Kafka's server-side cluster technology.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Kafka?
Why do developers choose Kafka Streams?
    Be the first to leave a pro

    Sign up to add, upvote and see more prosMake informed product decisions

      Be the first to leave a con
      What companies use Kafka?
      What companies use Kafka Streams?

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with Kafka?
      What tools integrate with Kafka Streams?

      Sign up to get full access to all the tool integrationsMake informed product decisions

      What are some alternatives to Kafka and Kafka Streams?
      ActiveMQ
      Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License.
      RabbitMQ
      RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
      Amazon Kinesis
      Amazon Kinesis can collect and process hundreds of gigabytes of data per second from hundreds of thousands of sources, allowing you to easily write applications that process information in real-time, from sources such as web site click-streams, marketing and financial information, manufacturing instrumentation and social media, and operational logs and metering data.
      Apache Spark
      Spark is a fast and general processing engine compatible with Hadoop data. It can run in Hadoop clusters through YARN or Spark's standalone mode, and it can process data in HDFS, HBase, Cassandra, Hive, and any Hadoop InputFormat. It is designed to perform both batch processing (similar to MapReduce) and new workloads like streaming, interactive queries, and machine learning.
      Akka
      Akka is a toolkit and runtime for building highly concurrent, distributed, and resilient message-driven applications on the JVM.
      See all alternatives
      Decisions about Kafka and Kafka Streams
      Roman Bulgakov
      Roman Bulgakov
      Senior Back-End Developer, Software Architect at Chemondis GmbH | 3 upvotes 10.5K views
      Kafka
      Kafka

      I use Kafka because it has almost infinite scaleability in terms of processing events (could be scaled to process hundreds of thousands of events), great monitoring (all sorts of metrics are exposed via JMX).

      Downsides of using Kafka are: - you have to deal with Zookeeper - you have to implement advanced routing yourself (compared to RabbitMQ it has no advanced routing)

      See more
      Kafka
      Kafka
      RabbitMQ
      RabbitMQ

      The question for which Message Queue to use mentioned "availability, distributed, scalability, and monitoring". I don't think that this excludes many options already. I does not sound like you would take advantage of Kafka's strengths (replayability, based on an even sourcing architecture). You could pick one of the AMQP options.

      I would recommend the RabbitMQ message broker, which not only implements the AMQP standard 0.9.1 (it can support 1.x or other protocols as well) but has also several very useful extensions built in. It ticks the boxes you mentioned and on top you will get a very flexible system, that allows you to build the architecture, pick the options and trade-offs that suite your case best.

      For more information about RabbitMQ, please have a look at the linked markdown I assembled. The second half explains many configuration options. It also contains links to managed hosting and to libraries (though it is missing Python's - which should be Puka, I assume).

      See more
      Fr茅d茅ric MARAND
      Fr茅d茅ric MARAND
      Core Developer at OSInet | 2 upvotes 120.7K views
      atOSInetOSInet
      Beanstalkd
      Beanstalkd
      RabbitMQ
      RabbitMQ
      Kafka
      Kafka

      I used Kafka originally because it was mandated as part of the top-level IT requirements at a Fortune 500 client. What I found was that it was orders of magnitude more complex ...and powerful than my daily Beanstalkd , and far more flexible, resilient, and manageable than RabbitMQ.

      So for any case where utmost flexibility and resilience are part of the deal, I would use Kafka again. But due to the complexities involved, for any time where this level of scalability is not required, I would probably just use Beanstalkd for its simplicity.

      I tend to find RabbitMQ to be in an uncomfortable middle place between these two extremities.

      See more
      Interest over time
      Reviews of Kafka and Kafka Streams
      No reviews found
      How developers use Kafka and Kafka Streams
      Avatar of Pinterest
      Pinterest uses KafkaKafka

      http://media.tumblr.com/d319bd2624d20c8a81f77127d3c878d0/tumblr_inline_nanyv6GCKl1s1gqll.png

      Front-end messages are logged to Kafka by our API and application servers. We have batch processing (on the middle-left) and real-time processing (on the middle-right) pipelines to process the experiment data. For batch processing, after daily raw log get to s3, we start our nightly experiment workflow to figure out experiment users groups and experiment metrics. We use our in-house workflow management system Pinball to manage the dependencies of all these MapReduce jobs.

      Avatar of Coolfront Technologies
      Coolfront Technologies uses KafkaKafka

      Building out real-time streaming server to present data insights to Coolfront Mobile customers and internal sales and marketing teams.

      Avatar of ShareThis
      ShareThis uses KafkaKafka

      We are using Kafka as a message queue to process our widget logs.

      Avatar of Christopher Davison
      Christopher Davison uses KafkaKafka

      Used for communications and triggering jobs across ETL systems

      Avatar of theskyinflames
      theskyinflames uses KafkaKafka

      Used as a integration middleware by messaging interchanging.

      How much does Kafka cost?
      How much does Kafka Streams cost?
      Pricing unavailable
      Pricing unavailable
      News about Kafka Streams
      More news