Channels (Pipes)

Thread-safe communication pipelines between concurrent goroutines.

Real-World Analogy (Mental Model)

“A pneumatic tube system in an office: drop a container tube in, and it whooshes across the room directly into the receiver hands without anyone sharing desks.”

Interactive Goroutine & Channel Simulator

Concurrent CSP

“Do not communicate by sharing memory; share memory by communicating.” Test how Go channels synchronize goroutines:

Channel: ch := make(chan string, 2)Buffer: 0 / 2 items

Sender G1 (Worker)

Slot 1

Slot 2

Receiver G2 (Main)

Runtime Log: Channel is idle. Send a message to get started.

Key Concepts & Rules To Remember

"Do not communicate by sharing memory; instead, share memory by communicating."
Unbuffered channels (`make(chan int)`) block until both sender and receiver are ready (rendezvous).
Buffered channels (`make(chan int, 5)`) hold items up to capacity before blocking.

Step-by-Step Code

1. Understanding Channels (Pipes)

Thread-safe communication pipelines between concurrent goroutines. In Go, channels (pipes) is designed around clarity and high runtime efficiency.

example.goGo 1.24+

ch := make(chan string)

go func() {
    ch <- "Task Completed!" // Send
}()

msg := <-ch // Receive (blocks until ready)
fmt.Println(msg)

Common Beginner Pitfalls & Mistakes

Mistake: Misusing channels (pipes) without understanding its memory or concurrency semantics.

✅ Correct Way: Always follow standard Go idioms and verify with tests.

Self Assessment

Knowledge Check

Verify your understanding with these interactive practice questions.

Quizzes

Quick checks for understanding

Multiple-choice with inline explanations—expand to see why.

What is the primary concept behind Channels (Pipes)?

Finished this lesson?

Mark it as complete to track your overall Go mastery.

PreviousGoroutines

Next Select