StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Utilities
  3. Background Jobs
  4. Message Queue
  5. CDAP vs Kafka

CDAP vs Kafka

OverviewDecisionsComparisonAlternatives

Overview

Kafka
Kafka
Stacks24.2K
Followers22.3K
Votes607
GitHub Stars31.2K
Forks14.8K
CDAP
CDAP
Stacks41
Followers108
Votes0

CDAP vs Kafka: What are the differences?

Introduction

Here are the key differences between CDAP and Kafka:

  1. Data Processing Paradigm: CDAP is an integrated platform for big data applications, providing a unified framework for data ingestion, processing, and analysis. It offers a visual interface for data pipelines and application development. On the other hand, Apache Kafka is a distributed event streaming platform that is designed for handling real-time data feeds. It focuses more on the publish-subscribe messaging model and low-latency data processing.

  2. Functional Focus: CDAP is more focused on providing a comprehensive solution for data integration, ETL (Extract, Transform, Load) processes, and building analytics applications. It supports batch processing, real-time processing, and interactive analytics. In contrast, Kafka emphasizes high-throughput data streaming, real-time event processing, and building scalable and fault-tolerant messaging systems for handling large volumes of data.

  3. Use Cases: CDAP is suitable for organizations looking to build end-to-end data pipelines, operationalize machine learning models, and develop complex data applications that require integration of various data sources. It is often used in industries such as healthcare, finance, and retail for data processing and analytics. On the other hand, Kafka is widely used in scenarios where real-time data processing, data integration, log aggregation, and messaging between microservices are critical requirements.

  4. Scalability and Performance: CDAP provides scalability through its distributed nature, enabling horizontal scaling of data processing workloads across multiple nodes. However, Kafka is inherently designed for high scalability and performance, allowing seamless horizontal scaling of data streaming and processing capabilities without downtime or data loss.

  5. Data Storage and Retention: CDAP includes various storage options like HDFS, HBase, and relational databases for storing processed data, intermediate results, and metadata. It offers flexibility in choosing the right storage backend based on the application requirements. In contrast, Kafka primarily relies on its own storage mechanism called "log compaction" for retaining messages over a defined period or until a certain condition is met, providing efficient message retention and replay capabilities.

  6. Ecosystem Integration: CDAP supports integration with a wide range of big data technologies such as Hadoop, Spark, and more, offering a comprehensive ecosystem for data processing and analytics. Kafka, on the other hand, is often integrated with various data processing frameworks and tools for stream processing, real-time analytics, and event-driven architectures, making it a central component in many data pipelines and streaming applications.

In Summary, the key differences between CDAP and Kafka lie in their data processing paradigms, functional focuses, use cases, scalability, data storage mechanisms, and ecosystem integrations.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Kafka, CDAP

viradiya
viradiya

Apr 12, 2020

Needs adviceonAngularJSAngularJSASP.NET CoreASP.NET CoreMSSQLMSSQL

We are going to develop a microservices-based application. It consists of AngularJS, ASP.NET Core, and MSSQL.

We have 3 types of microservices. Emailservice, Filemanagementservice, Filevalidationservice

I am a beginner in microservices. But I have read about RabbitMQ, but come to know that there are Redis and Kafka also in the market. So, I want to know which is best.

934k views934k
Comments
Ishfaq
Ishfaq

Feb 28, 2020

Needs advice

Our backend application is sending some external messages to a third party application at the end of each backend (CRUD) API call (from UI) and these external messages take too much extra time (message building, processing, then sent to the third party and log success/failure), UI application has no concern to these extra third party messages.

So currently we are sending these third party messages by creating a new child thread at end of each REST API call so UI application doesn't wait for these extra third party API calls.

I want to integrate Apache Kafka for these extra third party API calls, so I can also retry on failover third party API calls in a queue(currently third party messages are sending from multiple threads at the same time which uses too much processing and resources) and logging, etc.

Question 1: Is this a use case of a message broker?

Question 2: If it is then Kafka vs RabitMQ which is the better?

804k views804k
Comments
Roman
Roman

Senior Back-End Developer, Software Architect

Feb 12, 2019

ReviewonKafkaKafka

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)
10.9k views10.9k
Comments

Detailed Comparison

Kafka
Kafka
CDAP
CDAP

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

Cask Data Application Platform (CDAP) is an open source application development platform for the Hadoop ecosystem that provides developers with data and application virtualization to accelerate application development, address a broader range of real-time and batch use cases, and deploy applications into production while satisfying enterprise requirements.

Written at LinkedIn in Scala;Used by LinkedIn to offload processing of all page and other views;Defaults to using persistence, uses OS disk cache for hot data (has higher throughput then any of the above having persistence enabled);Supports both on-line as off-line processing
Streams for data ingestion;Reusable libraries for common Big Data access patterns;Data available to multiple applications and different paradigms;Framework level guarantees;Full development lifecycle and production deployment;Standardization of applications across programming paradigms
Statistics
GitHub Stars
31.2K
GitHub Stars
-
GitHub Forks
14.8K
GitHub Forks
-
Stacks
24.2K
Stacks
41
Followers
22.3K
Followers
108
Votes
607
Votes
0
Pros & Cons
Pros
  • 126
    High-throughput
  • 119
    Distributed
  • 92
    Scalable
  • 86
    High-Performance
  • 66
    Durable
Cons
  • 32
    Non-Java clients are second-class citizens
  • 29
    Needs Zookeeper
  • 9
    Operational difficulties
  • 5
    Terrible Packaging
No community feedback yet
Integrations
No integrations available
Hadoop
Hadoop

What are some alternatives to Kafka, CDAP?

RabbitMQ

RabbitMQ

RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

Celery

Celery

Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.

Amazon SQS

Amazon SQS

Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use.

NSQ

NSQ

NSQ is a realtime distributed messaging platform designed to operate at scale, handling billions of messages per day. It promotes distributed and decentralized topologies without single points of failure, enabling fault tolerance and high availability coupled with a reliable message delivery guarantee. See features & guarantees.

Apache Spark

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.

ActiveMQ

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.

ZeroMQ

ZeroMQ

The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more.

Presto

Presto

Distributed SQL Query Engine for Big Data

Apache NiFi

Apache NiFi

An easy to use, powerful, and reliable system to process and distribute data. It supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic.

Amazon Athena

Amazon Athena

Amazon Athena is an interactive query service that makes it easy to analyze data in Amazon S3 using standard SQL. Athena is serverless, so there is no infrastructure to manage, and you pay only for the queries that you run.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase