Lambda architecture (batch + streaming) in Hadoop - Time & Space Complexity

Time Complexity: Lambda architecture (batch + streaming)

O(n)

Understanding Time Complexity

We want to understand how the time needed to process data grows in a Lambda architecture using Hadoop.

Specifically, how batch and streaming parts affect the total work as data size increases.

Scenario Under Consideration

Analyze the time complexity of the following Hadoop code snippet for batch and streaming layers.

// Batch layer: process large data in Hadoop MapReduce
job.setMapperClass(BatchMapper.class);
job.setReducerClass(BatchReducer.class);
job.setInputFormatClass(TextInputFormat.class);
job.setOutputFormatClass(TextOutputFormat.class);

// Speed layer: process streaming data with small batches
StreamingJob streamingJob = new StreamingJob();
streamingJob.setMapperClass(StreamMapper.class);
streamingJob.setReducerClass(StreamReducer.class);
streamingJob.run();

This code runs two parts: batch jobs on big data sets and streaming jobs on small, fast data chunks.

Identify Repeating Operations

Look at the loops and repeated processing steps.

• Primary operation: Batch layer runs MapReduce over all data once per batch.
• How many times: Batch runs periodically on full data; streaming runs continuously on small data chunks.

How Execution Grows With Input

Batch layer time grows with total data size, streaming layer time grows with incoming data rate.

Input Size (n)	Approx. Batch Operations	Approx. Streaming Operations
10 GB	10 units	1 unit per small chunk
100 GB	100 units	1 unit per small chunk
1000 GB	1000 units	1 unit per small chunk

Batch work grows linearly with total data size; streaming work depends on how fast data arrives, not total size.

Final Time Complexity

Time Complexity: O(n)

This means the batch processing time grows linearly with the size of the data processed.

Common Mistake

[X] Wrong: "Streaming layer time grows the same as batch because it processes all data."

[OK] Correct: Streaming processes small, recent data chunks continuously, not the entire dataset, so its time depends on data arrival rate, not total size.

Interview Connect

Understanding how batch and streaming parts scale helps you explain real-world data processing systems clearly and confidently.

Self-Check

"What if the streaming layer started processing larger batches instead of small chunks? How would the time complexity change?"

Practice

1. What is the main purpose of the batch layer in Lambda architecture?

easy

A. To process all data for accurate and complete results

B. To handle real-time data streams quickly

C. To store raw data without processing

D. To visualize data for end users

Solution

1. Step 1: Understand batch layer role

   The batch layer processes all accumulated data to provide accurate and comprehensive views.

2. Step 2: Compare with other layers

   The speed layer handles real-time data, not the batch layer.

3. Final Answer:

   To process all data for accurate and complete results -> Option A

4. Quick Check:

   Batch layer = accurate full data processing [OK]

Hint: Batch layer = full data, accurate results [OK]

Common Mistakes:

• Confusing batch layer with speed layer
• Thinking batch layer processes data in real-time
• Assuming batch layer only stores raw data

2. Which of the following is the correct component of Lambda architecture for handling real-time data?

easy

A. Batch layer

B. Speed layer

C. Serving layer

D. Storage layer

Solution

1. Step 1: Identify real-time processing component

   The speed layer is designed to process data streams in real-time for quick insights.

2. Step 2: Eliminate other options

   Batch layer processes full data, serving layer provides query results, storage layer is not a standard Lambda component.

3. Final Answer:

   Speed layer -> Option B

4. Quick Check:

   Speed layer = real-time data processing [OK]

Hint: Speed layer = real-time data [OK]

Common Mistakes:

• Choosing batch layer for real-time data
• Confusing serving layer with speed layer
• Thinking storage layer is a Lambda component

3. Consider this simplified pseudocode for Lambda architecture layers:

batch_result = batch_layer(data)
speed_result = speed_layer(stream)
final_result = merge(batch_result, speed_result)
print(final_result)

If batch_layer returns {'count': 100} and speed_layer returns {'count': 5}, what will final_result be after merging by summing counts?

medium

A. {'count': 105}

B. {'count': 100}

C. {'count': 5}

D. Error: Cannot merge dictionaries

Solution

1. Step 1: Understand merging logic

   Merging sums the 'count' values from batch and speed results: 100 + 5 = 105.

2. Step 2: Confirm final result

   The final dictionary after merging is {'count': 105}.

3. Final Answer:

   {'count': 105} -> Option A

4. Quick Check:

   100 + 5 = 105 [OK]

Hint: Sum batch and speed counts for final result [OK]

Common Mistakes:

• Ignoring speed layer result
• Assuming merge replaces batch with speed
• Thinking merge causes error

4. This code snippet tries to implement the speed layer but has an error:

def speed_layer(stream):
    for record in stream:
        process(record)
    return processed_data

stream = get_stream()
result = speed_layer(stream)
print(result)

What is the likely error here?

medium

A. process() function is missing

B. stream is not iterable

C. processed_data is not defined before return

D. print() syntax error

Solution

1. Step 1: Check variable initialization

   The variable processed_data is returned but never defined or updated inside the function.

2. Step 2: Verify other parts

   Assuming stream is iterable and process() exists, the main error is missing processed_data definition.

3. Final Answer:

   processed_data is not defined before return -> Option C

4. Quick Check:

   Undefined variable causes error [OK]

Hint: Check all variables are defined before return [OK]

Common Mistakes:

• Assuming process() is missing without checking
• Thinking stream is not iterable
• Ignoring variable initialization

5. In a Lambda architecture, if the batch layer updates data every 24 hours and the speed layer processes data every second, what is the best way to ensure the serving layer shows the most accurate and up-to-date results?

hard

A. Use the speed layer results immediately and replace them with batch results after 24 hours

B. Only show batch layer results to avoid inconsistency

C. Ignore speed layer and rely on batch layer for all queries

D. Merge speed and batch results continuously, updating serving layer with combined data

Solution

1. Step 1: Understand serving layer role

   The serving layer combines batch and speed layer outputs to provide accurate and timely results.

2. Step 2: Evaluate options

   Merge speed and batch results continuously, updating serving layer with combined data merges both results continuously, ensuring the serving layer is both up-to-date and accurate.

3. Final Answer:

   Merge speed and batch results continuously, updating serving layer with combined data -> Option D

4. Quick Check:

   Serving layer = combined batch + speed data [OK]

Hint: Serving layer merges batch and speed data continuously [OK]

Common Mistakes:

• Using only speed or batch layer results alone
• Replacing speed results abruptly without merging
• Ignoring serving layer's combining role