Concurrency can be notoriously difficult to get right, but fortunately, the Go open source programming language makes working with concurrency tractable and even easy. If youre a developer familiar with Go, this practical book demonstrates best practices and patterns to help you incorporate concurrency into your systems.
Author Katherine Cox-Buday takes you step-by-step through the process. Youll understand how Go chooses to model concurrency, what issues arise from this model, and how you can compose primitives within this model to solve problems. Learn the skills and tooling you need to confidently write and implement concurrent systems of any size.
Understand how Go addresses fundamental problems that make concurrency difficult to do correctly Learn the key differences between concurrency and parallelism Dig into the syntax of Gos memory synchronization primitives Form patterns with these primitives to write maintainable concurrent code Compose patterns into a series of practices that enable you to write large, distributed systems that scale Learn the sophistication behind goroutines and how Gos runtime stitches everything together
| Preface |
|
vii | |
|
1 An Introduction to Concurrency |
|
|
1 | (22) |
|
Moore's Law, Web Scale, and the Mess We're In |
|
|
2 | (2) |
|
|
|
4 | (16) |
|
|
|
4 | (2) |
|
|
|
6 | (2) |
|
Memory Access Synchronization |
|
|
8 | (2) |
|
Deadlocks, Livelocks, and Starvation |
|
|
10 | (8) |
|
Determining Concurrency Safety |
|
|
18 | (2) |
|
Simplicity in the Face of Complexity |
|
|
20 | (3) |
|
2 Modeling Your Code: Communicating Sequential Processes |
|
|
23 | (14) |
|
The Difference Between Concurrency and Parallelism |
|
|
23 | (3) |
|
|
|
26 | (3) |
|
|
|
29 | (2) |
|
Go's Philosophy on Concurrency |
|
|
31 | (6) |
|
3 Go's Concurrency Building Blocks |
|
|
37 | (48) |
|
|
|
37 | (10) |
|
|
|
47 | (17) |
|
|
|
47 | (2) |
|
|
|
49 | (3) |
|
|
|
52 | (5) |
|
|
|
57 | (2) |
|
|
|
59 | (5) |
|
|
|
64 | (14) |
|
|
|
78 | (5) |
|
|
|
83 | (1) |
|
|
|
83 | (2) |
|
4 Concurrency Patterns in Go |
|
|
85 | (62) |
|
|
|
85 | (4) |
|
|
|
89 | (1) |
|
Preventing Goroutine Leaks |
|
|
90 | (4) |
|
|
|
94 | (3) |
|
|
|
97 | (3) |
|
|
|
100 | (14) |
|
Best Practices for Constructing Pipelines |
|
|
104 | (5) |
|
|
|
109 | (5) |
|
|
|
114 | (5) |
|
|
|
119 | (1) |
|
|
|
120 | (2) |
|
|
|
122 | (2) |
|
|
|
124 | (7) |
|
|
|
131 | (14) |
|
|
|
145 | (2) |
|
|
|
147 | (50) |
|
|
|
147 | (8) |
|
Timeouts and Cancellation |
|
|
155 | (6) |
|
|
|
161 | (11) |
|
|
|
172 | (2) |
|
|
|
174 | (14) |
|
Healing Unhealthy Goroutines |
|
|
188 | (6) |
|
|
|
194 | (3) |
|
6 Goroutines and the Go Runtime |
|
|
197 | (16) |
|
|
|
197 | (15) |
|
Stealing Tasks or Continuations? |
|
|
204 | (8) |
|
Presenting All of This to the Developer |
|
|
212 | (1) |
|
|
|
212 | (1) |
| A Appendix |
|
213 | (6) |
| Index |
|
219 | |
Katherine is a computer scientist currently working at Canonical (of Ubuntu fame) on Juju, a cloud orchestration system. Her hobbies include software engineering, creative writing, Go (igo, baduk, weiquei), and guitar, all of which she pursues intermittently and with various levels of dedication.
