Recursion vs Iteration When Each Wins in DSA Javascript - Key Differences

Recall & Review

beginner

What is recursion in simple terms?

Recursion is when a function calls itself to solve smaller parts of a problem until it reaches a simple case it can solve directly.

beginner

What is iteration in simple terms?

Iteration means repeating a set of instructions using loops like for or while until a condition is met.

intermediate

When is recursion better than iteration?

Recursion is better when the problem is naturally divided into similar smaller problems, like tree traversals or factorial calculation, making the code simpler and easier to understand.

intermediate

When is iteration better than recursion?

Iteration is better when you want to save memory and avoid the overhead of many function calls, especially for simple loops or when the problem can be solved with repeated steps.

intermediate

What is a risk of using recursion too much?

Using recursion too much can cause a stack overflow error because each function call uses memory, and too many calls can fill up the call stack.

Which method is usually easier to write for problems like tree traversal?

A Neither works

B Iteration

C Both are equally easy

D Recursion

Recursion naturally fits tree traversal because it breaks the problem into smaller similar parts.

What is a common downside of recursion compared to iteration?

A Cannot solve complex problems

B Runs slower because loops are slower

C Uses more memory due to function calls

D Always harder to understand

Recursion uses more memory because each call adds to the call stack.

Which approach is better for simple repeated steps like counting from 1 to 10?

A Iteration

B Both are equally good

C Recursion

D Neither works

Iteration is simpler and more efficient for simple repeated steps.

What happens if recursion goes too deep without a base case?

A Program runs faster

B Stack overflow error occurs

C Program ignores extra calls

D Recursion automatically stops

Without a base case, recursion keeps calling itself until the call stack is full, causing an error.

Which is true about iteration?

A It uses loops to repeat instructions

B It always uses less memory than recursion

C It cannot solve problems with repeated steps

D It is slower than recursion

Iteration uses loops like for or while to repeat instructions.

Explain when you would choose recursion over iteration and why.

Think about problems that naturally repeat themselves in smaller chunks.

Describe the risks of using recursion and how iteration can help avoid them.

Consider what happens when too many function calls happen.

Practice

1. Which scenario is best suited for using recursion instead of iteration?

easy

A. When the problem requires simple repeated loops

B. When the problem can be divided into smaller similar subproblems

C. When you want to avoid function call overhead

D. When memory usage must be minimal

Solution

1. Step 1: Understand recursion use case

   Recursion works well when a problem can be broken down into smaller versions of itself, like tree traversals or factorial calculation.

2. Step 2: Compare with iteration scenarios

   Iteration is better for simple repeated tasks without nested subproblems, so recursion is preferred for divide-and-conquer problems.

3. Final Answer:

   When the problem can be divided into smaller similar subproblems -> Option B

4. Quick Check:

   Recursion fits divide-and-conquer = C [OK]

Hint: Recursion fits problems breaking into smaller similar parts [OK]

Common Mistakes:

• Thinking iteration is always faster
• Ignoring function call overhead in recursion
• Confusing simple loops with recursive problems

2. Which of the following is the correct syntax for a recursive function in JavaScript?

easy

A. function recurse(n) { while(n > 0) { n--; } return n; }

B. function recurse(n) { for(let i=0; i

C. function recurse(n) { if (n <= 0) return 0; return n + recurse(n - 1); }

D. function recurse(n) { if(n > 0) { return n * recurse(n + 1); } else { return 1; } }

Solution

1. Step 1: Identify recursive call and base case

   function recurse(n) { if (n <= 0) return 0; return n + recurse(n - 1); } has a base case (n <= 0) and calls itself with a smaller argument (n - 1), which is correct recursion.

2. Step 2: Check other options for recursion errors

   function recurse(n) { while(n > 0) { n--; } return n; } uses a loop, not recursion. function recurse(n) { for(let i=0; i 0) { return n * recurse(n + 1); } else { return 1; } } calls recurse with n + 1, causing infinite recursion.

3. Final Answer:

   function recurse(n) { if (n <= 0) return 0; return n + recurse(n - 1); } -> Option C

4. Quick Check:

   Base case + smaller recursive call = B [OK]

Hint: Look for base case and smaller recursive call [OK]

Common Mistakes:

• Missing base case causing infinite recursion
• Using loops instead of recursive calls
• Increasing argument in recursive call causing stack overflow

3. What is the output of the following JavaScript code?

function factorial(n) {
  if (n === 0) return 1;
  return n * factorial(n - 1);
}
console.log(factorial(4));

medium

A. 24

B. 10

C. 16

D. Error

Solution

1. Step 1: Trace recursive calls for factorial(4)

   factorial(4) calls factorial(3), factorial(3) calls factorial(2), factorial(2) calls factorial(1), factorial(1) calls factorial(0) which returns 1.

2. Step 2: Calculate return values step-by-step

   factorial(1) = 1 * 1 = 1, factorial(2) = 2 * 1 = 2, factorial(3) = 3 * 2 = 6, factorial(4) = 4 * 6 = 24.

3. Final Answer:

   24 -> Option A

4. Quick Check:

   4! = 24 [OK]

Hint: Factorial n! = n * (n-1)! [OK]

Common Mistakes:

• Confusing factorial with sum
• Forgetting base case returns 1
• Miscomputing multiplication order

4. Identify the error in this recursive function and choose the fix:

function sumTo(n) {
  if (n === 1) return 1;
  return n + sumTo(n);
}

medium

A. Change return to console.log

B. Add a base case for n === 0

C. Replace recursion with a for loop

D. Change sumTo(n) to sumTo(n - 1) in the return statement

Solution

1. Step 1: Analyze recursive call argument

   The function calls sumTo(n) again without changing n, causing infinite recursion and stack overflow.

2. Step 2: Fix recursive call to reduce problem size

   Changing sumTo(n) to sumTo(n - 1) reduces n each call, eventually reaching base case n === 1.

3. Final Answer:

   Change sumTo(n) to sumTo(n - 1) in the return statement -> Option D

4. Quick Check:

   Recursive call must reduce argument = A [OK]

Hint: Recursive calls must progress toward base case [OK]

Common Mistakes:

• Calling function with same argument causing infinite loop
• Missing or wrong base case
• Confusing recursion with iteration fixes

5. You want to process a large list of numbers to find their sum. Which approach is better and why?

hard

A. Iteration is better because it uses less memory and avoids stack overflow

B. Recursion is better because it is easier to write for large lists

C. Recursion with memoization is best for summing lists

D. Recursive function without base case is best for performance

Solution

1. Step 1: Consider recursion limits for large lists

   Recursion uses call stack for each call, which can cause stack overflow for large lists.

2. Step 2: Compare iteration benefits

   Iteration uses constant memory and avoids stack overflow, making it safer and more efficient for large data.

3. Final Answer:

   Iteration is better because it uses less memory and avoids stack overflow -> Option A

4. Quick Check:

   Iteration safer for large data = A [OK]

Hint: Use iteration for large data to avoid stack overflow [OK]

Common Mistakes:

• Assuming recursion always simpler for large data
• Ignoring stack overflow risk
• Misusing memoization for simple sums