Why concurrency is needed in Go - Quick Recap

Recall & Review

beginner

What is concurrency in programming?

Concurrency means doing multiple tasks at the same time or overlapping in time to make programs faster and more efficient.

beginner

Why do we need concurrency in programs?

We need concurrency to handle many tasks at once, like serving many users or running background jobs, so programs don’t wait and waste time.

intermediate

How does concurrency improve program performance?

Concurrency lets programs use CPU and resources better by working on multiple things at once, reducing waiting time and speeding up results.

beginner

Give a real-life example of why concurrency is useful.

Like a restaurant kitchen where cooks prepare different dishes at the same time, concurrency lets a program handle many tasks without waiting for one to finish first.

beginner

What can happen if a program does not use concurrency?

Without concurrency, a program might do one task at a time, causing delays and making users wait longer for results.

Why is concurrency important in programming?

A To write shorter code

B To make programs use less memory

C To run multiple tasks at the same time

D To avoid using functions

Concurrency allows programs to run multiple tasks simultaneously, improving efficiency.

What is a simple real-life example of concurrency?

A One cook making all dishes one after another

B Reading a book silently

C Waiting for a bus

D Multiple cooks preparing different dishes at the same time

Multiple cooks working at once is like concurrency, handling many tasks simultaneously.

What happens if a program does not use concurrency?

A It runs tasks faster

B It does one task at a time causing delays

C It handles many users easily

D It uses multiple CPUs automatically

Without concurrency, tasks run one after another, causing slower performance.

Concurrency helps programs to:

A Use CPU resources better

B Use less disk space

C Avoid errors completely

D Write code without bugs

Concurrency improves CPU usage by running tasks in overlapping time.

Which of these is NOT a benefit of concurrency?

A Making code harder to read

B Handling multiple users at once

C Faster program response

D Better resource use

Concurrency can make code more complex, but this is not a benefit.

Explain in your own words why concurrency is needed in programming.

Think about how doing many things at the same time helps a program.

Describe a real-life situation that shows why concurrency is useful.

Imagine people working on different jobs at the same time.

Practice

1. Why do we need concurrency in Go programs?

easy

A. To simplify the code by removing all loops and conditions.

B. To allow multiple tasks to run at the same time, improving speed and responsiveness.

C. To make the program use less memory by running tasks one after another.

D. To avoid using functions and write everything in the main block.

Solution

1. Step 1: Understand concurrency purpose

   Concurrency allows a program to handle multiple tasks at once instead of waiting for one to finish before starting another.

2. Step 2: Relate concurrency to Go

   Go uses goroutines to run tasks concurrently, which helps programs be faster and more responsive.

3. Final Answer:

   To allow multiple tasks to run at the same time, improving speed and responsiveness. -> Option B

4. Quick Check:

   Concurrency = multiple tasks at once [OK]

Hint: Concurrency means doing many things at once [OK]

Common Mistakes:

• Thinking concurrency reduces memory by running tasks sequentially
• Confusing concurrency with simpler code structure
• Believing concurrency removes the need for functions

2. Which of the following is the correct way to start a goroutine in Go?

easy

A. go myFunction()

B. start myFunction()

C. run myFunction()

D. goroutine myFunction()

Solution

1. Step 1: Recall Go syntax for goroutines

   In Go, the keyword go is used before a function call to start it as a goroutine.

2. Step 2: Check each option

   Only go myFunction() uses the correct go keyword syntax; others are invalid in Go.

3. Final Answer:

   go myFunction() -> Option A

4. Quick Check:

   Start goroutine with 'go' keyword [OK]

Hint: Use 'go' before function to start goroutine [OK]

Common Mistakes:

• Using 'start' or 'run' instead of 'go'
• Forgetting the 'go' keyword before function call
• Trying to declare goroutine with 'goroutine' keyword

3. What will be the output of this Go program?

package main
import (
  "fmt"
  "time"
)
func sayHello() {
  fmt.Println("Hello")
}
func main() {
  go sayHello()
  time.Sleep(1 * time.Second)
  fmt.Println("World")
}

medium

A. World\nHello

B. Hello

C. Hello\nWorld

D. World

Solution

1. Step 1: Understand goroutine and sleep

   The function sayHello runs as a goroutine, so it runs concurrently with main. The main function sleeps 1 second to allow sayHello to print.

2. Step 2: Determine print order

   Because of the sleep, "Hello" prints first from the goroutine, then "World" prints after sleep ends.

3. Final Answer:

   Hello World -> Option C

4. Quick Check:

   Goroutine prints 'Hello' before main prints 'World' [OK]

Hint: Sleep lets goroutine finish before main prints [OK]

Common Mistakes:

• Ignoring time.Sleep and missing 'Hello' output
• Assuming 'World' prints before 'Hello'
• Thinking goroutine blocks main function

4. Identify the problem in this Go code snippet:

package main
import "fmt"
func main() {
  go func() {
    fmt.Println("Running")
  }()
  fmt.Println("Done")
}

medium

A. Goroutines cannot be used inside main function.

B. The anonymous function syntax is incorrect.

C. The fmt package is not imported properly.

D. The program may exit before the goroutine runs, so "Running" might not print.

Solution

1. Step 1: Analyze goroutine execution timing

   The goroutine runs concurrently, but main may finish and exit before the goroutine prints "Running".

2. Step 2: Check code correctness

   The anonymous function syntax and imports are correct; goroutines can run inside main.

3. Final Answer:

   The program may exit before the goroutine runs, so "Running" might not print. -> Option D

4. Quick Check:

   Program exit can stop goroutine early [OK]

Hint: Main may exit before goroutine finishes [OK]

Common Mistakes:

• Thinking anonymous function syntax is wrong
• Believing goroutines can't run in main
• Ignoring program exit timing

5. You want to download 3 files concurrently in Go and print "All done" only after all downloads finish. Which approach correctly uses concurrency to achieve this?

hard

A. Start 3 goroutines for downloads and use a sync.WaitGroup to wait for all to finish before printing "All done".

B. Call the download functions one after another without goroutines, then print "All done".

C. Start 3 goroutines but print "All done" immediately after starting them without waiting.

D. Use a for loop to start downloads but do not synchronize; rely on time.Sleep to wait.

Solution

1. Step 1: Understand concurrency with synchronization

   Starting goroutines runs downloads concurrently, but we must wait for all to finish before printing "All done".

2. Step 2: Use sync.WaitGroup for waiting

   sync.WaitGroup lets main wait until all goroutines complete, ensuring correct order.

3. Final Answer:

   Start 3 goroutines for downloads and use a sync.WaitGroup to wait for all to finish before printing "All done". -> Option A

4. Quick Check:

   WaitGroup synchronizes goroutines before final print [OK]

Hint: Use WaitGroup to wait for all goroutines [OK]

Common Mistakes:

• Not waiting for goroutines before printing
• Using sleep instead of proper synchronization
• Running downloads sequentially without concurrency