Home >Backend Development >Golang >Mutex vs. Channel: When Should You Choose Which?
When to Choose a Mutex vs. a Channel
Golang provides both sync.Mutex and channels for concurrent programming, presenting developers with a decision of which tool to use in different scenarios.
Mutex vs. Channel
Using a Mutex
Mutexes are ideal for situations where:
Examples
1. Simple Counter:
Mutexes can be used to implement a simple counter that ensures only one goroutine increments the counter at a time.
import "sync" var counter int var m sync.Mutex func incrementCounter() { m.Lock() counter++ m.Unlock() }
2. Ping Pong Game:
While channels are often used for ping-pong games, Mutexes can achieve the same functionality by guarding access to the shared ball object.
import "sync" type Ball struct { hits int } var ball Ball var m sync.Mutex func player1() { for { m.Lock() ball.hits++ fmt.Println("Player 1:", ball.hits) m.Unlock() } }
3. Simple Cache:
Mutexes can be used to implement a simple cache with thread-safe access to its contents.
import "sync" type Cache struct { m map[string]interface{} mu sync.Mutex } func (c *Cache) Get(key string) interface{} { c.mu.Lock() defer c.mu.Unlock() return c.m[key] }
Choosing Between a Mutex and a Channel
The choice between a mutex and a channel depends on the specific requirements of the task. Mutexes are suitable for scenarios where preventing race conditions and ensuring thread-safe access to shared data is paramount. Channels, on the other hand, excel in communication and data sharing between goroutines.
The above is the detailed content of Mutex vs. Channel: When Should You Choose Which?. For more information, please follow other related articles on the PHP Chinese website!