Concurrency Patterns

Part of the Go course

Goroutines and channels are raw materials, like wood and screws. Knowing what they are does not tell you how to build a chair. In practice, almost all concurrent Go code is assembled from a handful of recognisable shapes, and once you can name them you will see them in every real codebase you open, doing the same job each time.

This lesson covers five of those shapes. Waiting on whichever of several things happens first. Telling work to stop before it finishes. Waiting for a group of goroutines to be done. Protecting a value that two goroutines both write to. And handing a big pile of jobs to a fixed team of workers instead of hiring one worker per job.