Spark vs Hadoop MapReduce in Apache Spark - Quick Revision & Key Differences

Recall & Review

beginner

What is the main difference between Apache Spark and Hadoop MapReduce in terms of data processing?

Apache Spark processes data in-memory, making it faster, while Hadoop MapReduce reads and writes data to disk between each step, which is slower.

intermediate

How does Spark handle iterative algorithms compared to Hadoop MapReduce?

Spark keeps data in memory across iterations, speeding up iterative algorithms, whereas Hadoop MapReduce reloads data from disk each time, slowing down the process.

beginner

Which framework supports real-time stream processing: Spark or Hadoop MapReduce?

Apache Spark supports real-time stream processing through Spark Streaming, while Hadoop MapReduce is designed mainly for batch processing.

intermediate

What programming languages can you use with Apache Spark that are not natively supported by Hadoop MapReduce?

Apache Spark supports Scala, Python, Java, and R, while Hadoop MapReduce primarily supports Java.

advanced

Why might a company choose Hadoop MapReduce over Spark despite Spark's speed advantages?

Hadoop MapReduce can be more cost-effective for very large batch jobs on disk-based storage and has a mature ecosystem; also, it requires less memory than Spark.

Which of the following best describes Apache Spark's data processing?

A In-memory processing for faster computation

B Disk-based processing only

C Processes data one record at a time

D Only supports batch processing

Apache Spark processes data in memory, which speeds up computation compared to disk-based methods.

Hadoop MapReduce is best suited for which type of processing?

A Interactive querying

B Real-time streaming

C In-memory iterative processing

D Batch processing

Hadoop MapReduce is designed primarily for batch processing of large datasets.

Which language is NOT natively supported by Hadoop MapReduce but is supported by Spark?

A Java

B C++

C Scala

D Python

Spark supports Scala and Python natively, while Hadoop MapReduce mainly supports Java.

What feature allows Spark to speed up iterative algorithms?

A Disk caching

B Map-only jobs

C In-memory data storage

D Sequential processing

Spark stores data in memory across iterations, reducing disk reads and speeding up iterative tasks.

Which framework would be better for a company with limited memory resources?

A Apache Spark

B Hadoop MapReduce

C Both are equal

D Neither

Hadoop MapReduce uses disk storage and requires less memory, making it better for limited memory environments.

Explain the main performance differences between Apache Spark and Hadoop MapReduce.

Think about how each framework handles data during processing.

Describe scenarios where Hadoop MapReduce might be preferred over Apache Spark.

Consider resource availability and job types.

Practice

1. Which of the following is a key advantage of Apache Spark compared to Hadoop MapReduce?

easy

A. It cannot handle big data workloads.

B. It always uses disk storage for processing data.

C. It is slower but more stable than Spark.

D. It processes data faster by using memory instead of disk.

Solution

1. Step 1: Understand Spark's processing method

   Spark uses in-memory computation which speeds up data processing compared to disk-based methods.

2. Step 2: Compare with Hadoop MapReduce

   Hadoop MapReduce writes intermediate data to disk, making it slower but stable for large batch jobs.

3. Final Answer:

   It processes data faster by using memory instead of disk. -> Option D

4. Quick Check:

   Spark uses memory = Faster processing [OK]

Hint: Spark uses memory for speed; MapReduce uses disk [OK]

Common Mistakes:

• Thinking MapReduce is faster than Spark
• Assuming Spark always uses disk
• Believing Spark cannot handle big data

2. Which syntax correctly initializes a SparkContext in Python?

easy

A. sc = SparkContext.new()

B. sc = SparkContext()

C. sc = SparkContext.create()

D. sc = new SparkContext()

Solution

1. Step 1: Recall SparkContext initialization in PySpark

   The correct way is to call SparkContext() directly to create a new context.

2. Step 2: Check each option

   Options B and C use non-existent methods; D uses Java-like syntax not valid in Python.

3. Final Answer:

   sc = SparkContext() -> Option B

4. Quick Check:

   Correct Python syntax = sc = SparkContext() [OK]

Hint: Use SparkContext() directly in Python [OK]

Common Mistakes:

• Using Java syntax in Python
• Calling non-existent methods like new() or create()
• Forgetting to import SparkContext before use

3. Given the following code snippet in Spark, what will be the output?

rdd = sc.parallelize([1, 2, 3, 4])
result = rdd.map(lambda x: x * 2).collect()

medium

A. [1, 2, 3, 4]

B. [4, 8, 12, 16]

C. [2, 4, 6, 8]

D. [0, 2, 4, 6]

Solution

1. Step 1: Understand the map transformation

   The map applies the function x * 2 to each element in the RDD: 1*2=2, 2*2=4, 3*2=6, 4*2=8.

2. Step 2: Collect the results

   collect() gathers all transformed elements into a list: [2, 4, 6, 8].

3. Final Answer:

   [2, 4, 6, 8] -> Option C

4. Quick Check:

   Each element doubled = [2,4,6,8] [OK]

Hint: map applies function to each element [OK]

Common Mistakes:

• Confusing map with filter
• Forgetting to call collect() to get results
• Multiplying elements incorrectly

4. Identify the error in this Hadoop MapReduce pseudo-code snippet:

map(key, value):
  emit(value, key)

reduce(key, values):
  sum = 0
  for v in values:
    sum += v
  emit(key, sum)

medium

A. The reduce function sums values but values are keys from map output.

B. The map function emits key and value in wrong order.

C. The reduce function tries to sum keys instead of values.

D. There is no error; code is correct.

Solution

1. Step 1: Analyze map output

   Map emits (value, key), so keys in reduce are original values, and values are original keys.

2. Step 2: Check reduce summation

   Reduce sums 'values', but these are original keys, likely non-numeric or not intended for summation.

3. Final Answer:

   The reduce function sums values but values are keys from map output. -> Option A

4. Quick Check:

   Reduce sums wrong data = error [OK]

Hint: Check what map emits vs what reduce receives [OK]

Common Mistakes:

• Assuming map output keys and values are unchanged
• Summing keys instead of values
• Ignoring data types of reduce inputs

5. You have a large dataset to process repeatedly with iterative algorithms. Which framework is better and why?

hard

A. Apache Spark, because it caches data in memory for faster iterative processing.

B. Apache Spark, because it uses disk storage to handle iterative jobs.

C. Hadoop MapReduce, because it is easier to program for iterative tasks.

D. Hadoop MapReduce, because it writes intermediate results to disk for reliability.

Solution

1. Step 1: Understand iterative algorithm needs

   Iterative algorithms reuse data multiple times, so fast access is important.

2. Step 2: Compare Spark and MapReduce for iteration

   Spark caches data in memory, speeding up repeated access; MapReduce writes to disk each time, slowing down iteration.

3. Final Answer:

   Apache Spark, because it caches data in memory for faster iterative processing. -> Option A

4. Quick Check:

   Memory caching = faster iteration [OK]

Hint: Use Spark for fast iterative jobs with memory caching [OK]

Common Mistakes:

• Choosing MapReduce for iterative speed
• Confusing disk use with speed
• Thinking Spark uses disk for iteration