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

Samza

24
62
+ 1
0
Apache Spark

3K
3.5K
+ 1
140
Add tool

Apache Spark vs Samza: What are the differences?

Introduction

Apache Spark and Samza are both powerful distributed computing frameworks commonly used in big data processing. They differ in various aspects that cater to different use cases and requirements.

  1. Processing Model: Apache Spark is primarily designed for in-memory processing of data, making it suitable for iterative algorithms and interactive data analysis. On the other hand, Samza focuses on stream processing, enabling real-time processing of large volumes of data with low latency.

  2. Fault Tolerance: Spark provides fault tolerance through resilient distributed datasets (RDDs), offering fault recovery at the granularity of RDDs. Samza, on the other hand, provides fault tolerance through checkpoints, allowing it to resume processing from the last checkpoint in case of failures.

  3. Batch vs. Streaming: While Spark can handle both batch and streaming data processing, it is more optimized for batch processing compared to streaming. Samza, on the other hand, is specifically designed for stream processing, making it more efficient for real-time data processing requirements.

  4. Programming Language Support: Apache Spark supports multiple programming languages like Scala, Java, Python, and R, making it versatile for developers with different preferences. Samza is heavily focused on Java and allows for seamless integration with existing Java-based applications and infrastructure.

  5. State Management: Spark does not provide built-in state management capabilities for stream processing, requiring users to integrate external systems for state handling. In contrast, Samza comes with built-in state management capabilities, making it easier for users to manage and store state information within the framework.

  6. Use Cases: Apache Spark is suitable for a wide range of use cases, including machine learning, interactive data analysis, and batch processing, making it a versatile choice for various data processing requirements. Samza, on the other hand, is more specialized for stream processing use cases that require low-latency real-time processing of data streams.

In Summary, Apache Spark and Samza differ in their processing models, fault tolerance mechanisms, focus on batch vs. streaming processing, programming language support, state management capabilities, and specific use cases they cater to in the realm of distributed computing.

Advice on Samza and Apache Spark
Nilesh Akhade
Technical Architect at Self Employed · | 5 upvotes · 558.6K 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 · 394.8K 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
Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of Samza
Pros of Apache Spark
    Be the first to leave a pro
    • 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 Samza
    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 Samza?

      It allows you to build stateful applications that process data in real-time from multiple sources including Apache Kafka.

      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 Samza?
      What companies use Apache Spark?
      Manage your open source components, licenses, and vulnerabilities
      Learn More

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

      What tools integrate with Samza?
      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
      2228
      MySQLKafkaApache Spark+6
      2
      2080
      Aug 28 2019 at 3:10AM

      Segment

      PythonJavaAmazon S3+16
      7
      2652
      What are some alternatives to Samza and Apache Spark?
      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.
      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.
      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.
      Kafka
      Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
      Akutan
      A distributed knowledge graph store. Knowledge graphs are suitable for modeling data that is highly interconnected by many types of relationships, like encyclopedic information about the world.
      See all alternatives