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

Apache Storm

202
282
+ 1
25
Apache Spark

2.9K
3.5K
+ 1
140
Add tool

Apache Spark vs Apache Storm: What are the differences?

Introduction: Apache Spark and Apache Storm are two prominent big data processing frameworks that differ in their architecture, use cases, and capabilities. Understanding the key differences between them is crucial for choosing the right tool for specific data processing needs.

  1. Processing Model: Apache Spark is a batch processing framework that primarily focuses on processing large datasets efficiently using in-memory computing. In contrast, Apache Storm is a real-time processing framework designed for handling continuous streams of data with low latency requirements, making it suitable for real-time analytics and event processing.

  2. Fault Tolerance: Apache Spark achieves fault tolerance through its resilient distributed dataset (RDD) abstraction, which allows data to be automatically recovered in case of node failures. On the other hand, Apache Storm provides fault tolerance through tuple tracking and acknowledgments, ensuring data processing continuity even in the event of failures.

  3. Data Processing Approach: Apache Spark utilizes a DAG (Directed Acyclic Graph) execution engine that optimizes task execution for batch processing. In contrast, Apache Storm follows a stream processing model where data is processed as it arrives, enabling real-time analytics and data transformations.

  4. Programming Languages: Apache Spark supports multiple programming languages such as Scala, Java, Python, and R, providing flexibility for developers to choose the language of their preference. Apache Storm primarily uses Java as its programming language, limiting the options for developers who prefer other languages for big data processing.

  5. Ecosystem Integration: Apache Spark has a rich ecosystem with libraries such as Apache Spark SQL, MLlib, GraphX, and Spark Streaming, providing comprehensive support for various data processing and analytics tasks. While Apache Storm is more focused on real-time data processing, it can be integrated with external systems such as databases, message queues, and monitoring tools to enhance its capabilities.

  6. Scalability: Apache Spark provides scalability through its distributed computing model and the ability to leverage cluster resources efficiently for processing large datasets. Apache Storm is designed for horizontal scalability, allowing users to scale out by adding more worker nodes to handle increasing data processing requirements effectively.

In Summary, Apache Spark and Apache Storm differ in their processing models, fault tolerance mechanisms, data processing approaches, programming language support, ecosystem integration, and scalability options, making them suitable for distinct use cases in big data processing.

Advice on Apache Storm and Apache Spark
Nilesh Akhade
Technical Architect at Self Employed · | 5 upvotes · 528.8K views

We have a Kafka topic having events of type A and type B. We need to perform an inner join on both type of events using some common field (primary-key). The joined events to be inserted in Elasticsearch.

In usual cases, type A and type B events (with same key) observed to be close upto 15 minutes. But in some cases they may be far from each other, lets say 6 hours. Sometimes event of either of the types never come.

In all cases, we should be able to find joined events instantly after they are joined and not-joined events within 15 minutes.

See more
Replies (2)
Recommends
on
ElasticsearchElasticsearch

The first solution that came to me is to use upsert to update ElasticSearch:

  1. Use the primary-key as ES document id
  2. Upsert the records to ES as soon as you receive them. As you are using upsert, the 2nd record of the same primary-key will not overwrite the 1st one, but will be merged with it.

Cons: The load on ES will be higher, due to upsert.

To use Flink:

  1. Create a KeyedDataStream by the primary-key
  2. In the ProcessFunction, save the first record in a State. At the same time, create a Timer for 15 minutes in the future
  3. When the 2nd record comes, read the 1st record from the State, merge those two, and send out the result, and clear the State and the Timer if it has not fired
  4. When the Timer fires, read the 1st record from the State and send out as the output record.
  5. Have a 2nd Timer of 6 hours (or more) if you are not using Windowing to clean up the State

Pro: if you have already having Flink ingesting this stream. Otherwise, I would just go with the 1st solution.

See more
Akshaya Rawat
Senior Specialist Platform at Publicis Sapient · | 3 upvotes · 371.2K views
Recommends
on
Apache SparkApache Spark

Please refer "Structured Streaming" feature of Spark. Refer "Stream - Stream Join" at https://spark.apache.org/docs/latest/structured-streaming-programming-guide.html#stream-stream-joins . In short you need to specify "Define watermark delays on both inputs" and "Define a constraint on time across the two inputs"

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Apache Storm
Pros of Apache Spark
  • 10
    Flexible
  • 6
    Easy setup
  • 4
    Event Processing
  • 3
    Clojure
  • 2
    Real Time
  • 61
    Open-source
  • 48
    Fast and Flexible
  • 8
    One platform for every big data problem
  • 8
    Great for distributed SQL like applications
  • 6
    Easy to install and to use
  • 3
    Works well for most Datascience usecases
  • 2
    Interactive Query
  • 2
    Machine learning libratimery, Streaming in real
  • 2
    In memory Computation

Sign up to add or upvote prosMake informed product decisions

Cons of Apache Storm
Cons of Apache Spark
    Be the first to leave a con
    • 4
      Speed

    Sign up to add or upvote consMake informed product decisions

    What is Apache Storm?

    Apache Storm is a free and open source distributed realtime computation system. Storm makes it easy to reliably process unbounded streams of data, doing for realtime processing what Hadoop did for batch processing. Storm has many use cases: realtime analytics, online machine learning, continuous computation, distributed RPC, ETL, and more. Storm is fast: a benchmark clocked it at over a million tuples processed per second per node. It is scalable, fault-tolerant, guarantees your data will be processed, and is easy to set up and operate.

    What is 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.

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

    What companies use Apache Storm?
    What companies use Apache Spark?
    See which teams inside your own company are using Apache Storm or Apache Spark.
    Sign up for StackShare EnterpriseLearn More

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

    What tools integrate with Apache Storm?
    What tools integrate with Apache Spark?

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

    Blog Posts

    Mar 24 2021 at 12:57PM

    Pinterest

    GitJenkinsKafka+7
    3
    2161
    MySQLKafkaApache Spark+6
    2
    2019
    Aug 28 2019 at 3:10AM

    Segment

    PythonJavaAmazon S3+16
    7
    2569
    What are some alternatives to Apache Storm and Apache Spark?
    Kafka
    Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
    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 Flume
    It is a distributed, reliable, and available service for efficiently collecting, aggregating, and moving large amounts of log data. It has a simple and flexible architecture based on streaming data flows. It is robust and fault tolerant with tunable reliability mechanisms and many failover and recovery mechanisms. It uses a simple extensible data model that allows for online analytic application.
    Apache Flink
    Apache Flink is an open source system for fast and versatile data analytics in clusters. Flink supports batch and streaming analytics, in one system. Analytical programs can be written in concise and elegant APIs in Java and Scala.
    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.
    See all alternatives