Coroutines vs threads mental model in Kotlin - Quick Revision & Key Differences

Recall & Review

beginner

What is a thread in Kotlin?

A thread is a real operating system unit of execution that runs code independently and can run in parallel with other threads.

beginner

What is a coroutine in Kotlin?

A coroutine is a lightweight, cooperative unit of work that can pause and resume without blocking a thread.

intermediate

How do coroutines differ from threads in resource usage?

Coroutines use much less memory and resources than threads because many coroutines can run on a few threads by suspending and resuming.

intermediate

Explain the mental model of coroutines compared to threads.

Think of threads as real workers who can work at the same time, while coroutines are like tasks that can pause their work and let others run on the same worker.

intermediate

Why are coroutines considered cooperative multitasking?

Because coroutines decide when to pause and resume, they cooperate to share threads without preemptive interruption.

Which of the following best describes a thread?

A A lightweight task that can pause and resume without blocking

B A real OS-level unit of execution that can run in parallel

C A function that runs only on the main thread

D A UI element in Kotlin

Threads are real OS units that run code independently and can run in parallel.

What is a key advantage of coroutines over threads?

A They are lightweight and can suspend without blocking

B They block threads when waiting

C They run only on a single thread

D They use more memory

Coroutines are lightweight and can suspend without blocking threads, making them efficient.

How do coroutines achieve multitasking?

A By blocking the main thread

B By running on separate CPU cores simultaneously

C By creating new threads for each task

D By cooperating and suspending to share threads

Coroutines cooperate by suspending and resuming to share threads efficiently.

Which statement is true about threads and coroutines?

A Threads are lighter than coroutines

B Coroutines always run on separate threads

C Coroutines can run many tasks on fewer threads

D Threads cannot run in parallel

Coroutines are lightweight and can run many tasks on fewer threads by suspending and resuming.

Why are coroutines called cooperative multitasking?

A Because they decide when to pause and resume

B Because they preempt threads forcibly

C Because they run only on the main thread

D Because they block other coroutines

Coroutines cooperate by choosing when to pause and resume, sharing threads smoothly.

Explain the difference between coroutines and threads using a simple real-life analogy.

Think about workers and tasks sharing time.

Describe why coroutines are more efficient than threads for many small tasks.

Focus on how coroutines save memory and CPU.

Practice

1. Which statement best describes the difference between Kotlin coroutines and threads?

easy

A. Both coroutines and threads are managed by the OS and have the same weight.

B. Threads are lightweight and managed by Kotlin, coroutines are heavier and managed by the OS.

C. Coroutines are lightweight and managed by Kotlin, threads are heavier and managed by the OS.

D. Coroutines and threads are the same and can be used interchangeably without difference.

Solution

1. Step 1: Understand management of coroutines and threads

   Coroutines are managed by Kotlin's runtime, making them lightweight tasks.

2. Step 2: Understand thread management

   Threads are managed by the operating system and are heavier compared to coroutines.

3. Final Answer:

   Coroutines are lightweight and managed by Kotlin, threads are heavier and managed by the OS. -> Option C

4. Quick Check:

   Coroutines lightweight, threads OS-managed = A [OK]

Hint: Coroutines are Kotlin tasks; threads are OS tasks [OK]

Common Mistakes:

• Confusing which manages coroutines vs threads
• Thinking coroutines are OS threads
• Assuming threads are lightweight like coroutines

2. Which Kotlin code snippet correctly launches a coroutine?

easy

A. coroutineStart { println("Start") }

B. Thread { println("Hello from thread") }.start()

C. runBlocking { Thread.sleep(1000) }

D. launch { println("Hello from coroutine") }

Solution

1. Step 1: Identify coroutine launch syntax

   The correct way to start a coroutine in Kotlin is using the 'launch' builder inside a coroutine scope.

2. Step 2: Check other options for correctness

   Thread { println("Hello from thread") }.start() starts a thread, not a coroutine. runBlocking { Thread.sleep(1000) } uses runBlocking with Thread.sleep, which blocks a thread. coroutineStart { println("Start") } is invalid syntax.

3. Final Answer:

   launch { println("Hello from coroutine") } -> Option D

4. Quick Check:

   launch starts coroutine = A [OK]

Hint: Use 'launch' to start coroutines, not Thread or unknown keywords [OK]

Common Mistakes:

• Using Thread instead of launch for coroutines
• Confusing runBlocking with coroutine launch
• Using invalid coroutine syntax

3. What will be the output of this Kotlin code snippet?

import kotlinx.coroutines.*
fun main() = runBlocking {
  launch {
    delay(100)
    println("Coroutine finished")
  }
  println("Main finished")
}

medium

A. Main finished
Coroutine finished

B. Coroutine finished
Main finished

C. Main finished

D. Coroutine finished

Solution

1. Step 1: Understand runBlocking and launch behavior

   runBlocking blocks the main thread until its coroutine completes. The launch coroutine delays 100ms before printing.

2. Step 2: Trace output order

   "Main finished" prints immediately. After 100ms delay, "Coroutine finished" prints. runBlocking waits for launch to complete before exiting.

3. Final Answer:

   Main finished Coroutine finished -> Option A

4. Quick Check:

   runBlocking waits, delay delays launch = C [OK]

Hint: runBlocking waits; launch delays print [OK]

Common Mistakes:

• Assuming launch runs before main print
• Ignoring delay effect
• Thinking runBlocking doesn't wait

4. Identify the error in this Kotlin coroutine code:

fun main() {
  launch {
    println("Hello")
  }
}

medium

A. Missing coroutine scope to launch coroutine

B. Incorrect use of println inside coroutine

C. launch should be replaced with Thread

D. No error, code runs fine

Solution

1. Step 1: Check coroutine launch context

   launch must be called inside a coroutine scope or suspend function. Here, main is a regular function without scope.

2. Step 2: Identify missing coroutine scope

   Without a scope like runBlocking or CoroutineScope, launch cannot start a coroutine.

3. Final Answer:

   Missing coroutine scope to launch coroutine -> Option A

4. Quick Check:

   launch needs coroutine scope = B [OK]

Hint: launch needs coroutine scope like runBlocking [OK]

Common Mistakes:

• Trying to launch coroutine outside scope
• Replacing launch with Thread incorrectly
• Thinking println causes error

5. You want to perform multiple network calls concurrently without blocking the main thread. Which approach best uses Kotlin coroutines to achieve this?

hard

A. Create multiple threads and use Thread.sleep to wait for results

B. Launch multiple coroutines with async and await their results

C. Use a single coroutine and call blocking network functions sequentially

D. Run network calls on the main thread directly

Solution

1. Step 1: Understand concurrency with coroutines

   Using async inside coroutines allows concurrent execution and returns Deferred results.

2. Step 2: Compare options for efficiency and correctness

   Create multiple threads and use Thread.sleep to wait for results uses threads and blocking sleep, which is heavy and inefficient. Use a single coroutine and call blocking network functions sequentially blocks sequentially, losing concurrency. Run network calls on the main thread directly blocks main thread, causing UI freeze.

3. Final Answer:

   Launch multiple coroutines with async and await their results -> Option B

4. Quick Check:

   async + await = concurrent coroutines [OK]

Hint: Use async/await for concurrent coroutines, not threads [OK]

Common Mistakes:

• Using threads with sleep instead of coroutines
• Blocking main thread with network calls
• Running network calls sequentially inside one coroutine