Spark vs Hadoop MapReduce in Apache Spark - Visual Side-by-Side Comparison

Concept Flow - Spark vs Hadoop MapReduce

Input Data

↓

Map Phase

↓

Shuffle & Sort

↓

Reduce Phase

↓

Write Output

↓

Final Result

Shows the flow of data processing in Hadoop MapReduce versus Apache Spark, highlighting disk-based steps versus in-memory operations.

Execution Sample

Apache Spark

data = sc.textFile('data.txt')
words = data.flatMap(lambda line: line.split())
wordCounts = words.map(lambda w: (w,1)).reduceByKey(lambda a,b: a+b)
wordCounts.collect()

Counts words in a text file using Spark's in-memory transformations and actions.

Execution Table

Step	Operation	Data Location	Action	Result
1	Read data from 'data.txt'	Disk	Load text file into RDD	RDD with lines of text
2	flatMap split lines	Memory	Split each line into words	RDD with words
3	map to (word,1)	Memory	Create pairs for counting	RDD of (word,1) tuples
4	reduceByKey sum counts	Memory	Sum counts for each word	RDD of (word, total_count)
5	collect results	Memory to Driver	Bring results to driver program	List of (word, count) pairs

💡 All transformations are lazy; action 'collect' triggers execution and returns final counts.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
data	empty	RDD(lines of text)	RDD(lines of text)	RDD(lines of text)	RDD(lines of text)	RDD(lines of text)
words	undefined	undefined	RDD(words)	RDD(words)	RDD(words)	RDD(words)
wordCounts	undefined	undefined	undefined	RDD((word,1))	RDD((word, total_count))	RDD((word, total_count))
result	undefined	undefined	undefined	undefined	undefined	List((word, count))

Key Moments - 3 Insights

Why does Spark run faster than Hadoop MapReduce?

Spark keeps data in memory during processing (see execution_table steps 2-4), avoiding slow disk reads/writes after each step, unlike Hadoop MapReduce which writes intermediate results to disk.

What triggers the actual computation in Spark?

Transformations like flatMap and map are lazy and do not run immediately. The action 'collect' (step 5 in execution_table) triggers all previous steps to execute.

Why does Hadoop MapReduce have shuffle and sort between map and reduce?

Because Hadoop writes intermediate data to disk and needs to organize it for reducers, causing extra disk I/O and latency, unlike Spark which keeps data in memory.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does Spark actually perform the word count aggregation?

A Step 2: flatMap split lines

B Step 4: reduceByKey sum counts

C Step 3: map to (word,1)

D Step 5: collect results

💡 Hint

Check the 'Action' column in execution_table for where counts are summed.

According to variable_tracker, what is the state of 'words' after Step 3?

A RDD((word,1))

B RDD(lines of text)

C RDD(words)

D List((word, count))

💡 Hint

Look at the 'words' row and the 'After Step 3' column in variable_tracker.

If we remove the 'collect' action, what happens to the execution according to the exit_note?

A No computation runs, transformations are lazy

B Only map runs, reduce does not

C All transformations run immediately

D Data is written to disk

💡 Hint

Refer to the exit_note about lazy transformations and action triggering.

Concept Snapshot

Spark vs Hadoop MapReduce:
- Hadoop MapReduce reads/writes intermediate data to disk.
- Spark keeps data in memory for faster processing.
- Spark uses lazy transformations; actions trigger execution.
- MapReduce has map, shuffle/sort, reduce phases.
- Spark uses RDD/DataFrame transformations and actions.
- Spark is generally faster for iterative and interactive tasks.

Full Transcript

This visual execution compares Apache Spark and Hadoop MapReduce data processing flows. Hadoop MapReduce reads input from disk, maps data, shuffles and sorts intermediate results on disk, then reduces and writes output. Spark reads data into memory as RDDs, applies transformations like flatMap and map lazily, then performs reduceByKey in memory. The action 'collect' triggers execution and returns results. Variables like 'data', 'words', and 'wordCounts' change state step-by-step in memory. Key points include Spark's speed advantage due to in-memory processing and lazy evaluation. The quiz tests understanding of when aggregation happens, variable states, and the role of actions in Spark.