Why concurrency is needed in Go - Visual Breakdown

Concept Flow - Why concurrency is needed

Start Program

↓

Task 1 Begins

↓

Task 2 Begins

↓

Tasks run sequentially?

↓

Wait long

↓

Slow program

↓

Better resource use

↓

Program ends

Shows how running tasks one after another slows a program, but running them at the same time (concurrency) makes it faster and uses resources better.

Execution Sample

Go

package main
import (
 "fmt"
 "time"
)
func main() {
 fmt.Println("Start")
 time.Sleep(2 * time.Second) // Task 1
 fmt.Println("Task 1 done")
 time.Sleep(2 * time.Second) // Task 2
 fmt.Println("Task 2 done")
}

This code runs two tasks one after another, each taking 2 seconds, so total time is about 4 seconds.

Execution Table

Step	Action	Time Passed (seconds)	Output
1	Print "Start"	0	Start
2	Sleep 2 seconds (Task 1)	2
3	Print "Task 1 done"	2	Task 1 done
4	Sleep 2 seconds (Task 2)	4
5	Print "Task 2 done"	4	Task 2 done
6	Program ends	4

💡 Both tasks run one after another, total time is 4 seconds.

Variable Tracker

Variable	Start	After Task 1	After Task 2	End
Time Passed (seconds)	0	2	4	4
Output	""	"Start\nTask 1 done\n"	"Start\nTask 1 done\nTask 2 done\n"	"Start\nTask 1 done\nTask 2 done\n"

Key Moments - 2 Insights

Why does the program take 4 seconds instead of 2?

Because Task 1 and Task 2 run one after another (see execution_table rows 2 and 4), so their times add up.

What if tasks could run at the same time?

Then total time would be about 2 seconds, not 4, because both tasks happen together, saving time.

Visual Quiz - 3 Questions

Look at the execution_table, what is printed at step 3?

A "Task 2 done"

B "Task 1 done"

C "Start"

D Nothing

💡 Hint

Check the Output column at step 3 in execution_table.

At which step does the program finish sleeping for Task 2?

A Step 4

B Step 2

C Step 5

D Step 6

💡 Hint

Look at the Action and Time Passed columns in execution_table.

If Task 1 and Task 2 ran concurrently, how would total time change?

A It would stay 4 seconds

B It would be about 1 second

C It would be about 2 seconds

D It would be 0 seconds

💡 Hint

Think about running tasks at the same time as explained in key_moments.

Concept Snapshot

Concurrency lets multiple tasks run at the same time.
Without concurrency, tasks run one after another, adding up time.
With concurrency, total time can be shorter.
This improves program speed and resource use.
In Go, concurrency is easy with goroutines.

Full Transcript

This example shows why concurrency is needed. The program runs two tasks, each taking 2 seconds, one after another. So total time is 4 seconds. If tasks ran at the same time, total time would be about 2 seconds. Concurrency helps programs run faster and use resources better by doing multiple things at once.

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