Custom Dispatcher in Kotlin

Introduction

Custom Dispatcher is a fundamental concept every Kotlin developer should understand. Dispatchers decide which thread pool runs coroutine code — Main for UI, IO for blocking work, and Default for CPU-bound tasks.

Custom dispatchers can be created using Executors and asCoroutineDispatcher(). In this tutorial you will learn the syntax, walk through a complete example program, study the sample output, and review best practices so you can apply the concept confidently in your own projects.

Definition

• Custom dispatchers can be created using Executors and asCoroutineDispatcher().
• Useful for dedicated thread pools.
• Always close custom dispatchers when no longer needed.

Syntax

Executors.newFixedThreadPool(n).asCoroutineDispatcher()

Custom Dispatcher in Kotlin Example Program in Kotlin

import kotlinx.coroutines.*
import java.util.concurrent.Executors

fun main(args: Array<String>) = runBlocking {
    val dispatcher = Executors.newFixedThreadPool(2).asCoroutineDispatcher()
    try {
        launch(dispatcher) {
            println("Custom dispatcher task")
        }
    } finally {
        dispatcher.close()
    }
}

Sample Output

Custom dispatcher task

When to use

Switch dispatchers when moving between UI updates (Main) and blocking or CPU-heavy work (IO / Default).

How it works

1. The program starts with a main function — the entry point that runs when you execute the file.

2. val dispatcher = Executors.newFixedThreadPool(2).asCoroutineDispatcher() assigns or updates a value used later in the program.

3. launch(dispatcher) { shows coroutine-based concurrency — work runs without blocking the calling thread.

4. The println("Custom dispatcher task") statement writes a line to the console — this produces part of the sample output below.

5. Custom dispatchers can be created using Executors and asCoroutineDispatcher().

6. Run the program in IntelliJ IDEA, Android Studio, or with the Kotlin command-line compiler (kotlinc / kotlin). Compare your console output with the sample output shown below.

Best Practices

• Understand the core idea: custom dispatchers can be created using Executors and asCoroutineDispatcher().
• Prefer readable names and small functions so examples map directly to real projects.
• Run and modify the example — change values and observe how the output changes.

Common Mistakes

• Skipping the example and only reading the definition — hands-on practice cements the concept.
• Copying syntax without understanding nullable vs non-nullable types or scope rules.
• Ignoring compiler warnings that often point to safer alternatives.

Key Points

• Custom dispatchers can be created using Executors and asCoroutineDispatcher().
• Useful for dedicated thread pools.
• Always close custom dispatchers when no longer needed.
• Test the example locally and verify the output matches the sample.
• Experiment by changing input values to see how behaviour changes.

Notes

• Add the kotlinx-coroutines-core dependency when running coroutine examples outside Android or IntelliJ.
• Semicolons at the end of statements are optional in Kotlin.