Gain insights into implementing concurrency in Go, explore common patterns, and learn to write efficient, practical applications leveraging Go's outstanding support for concurrency.

Go.tar.gz

DataRaceBuilder

temp

Mastering concurrency can make you a much more in-demand developer on the job market. It's becoming an increasingly important concept in modern programming as multi-core devices become more and more prevalent.

The good news is that Go has some outstanding support for concurrency out of the box that makes implementation a breeze. In fact, concurrency in Go is easier to implement and faster than in any other major language.

In this course, you'll start off with a general introduction to concurrency and build up to more advanced concepts and implementation in Go. You'll also have a chance to go through some common patterns that will make your life easier and your code more efficient. By the time you're done, you'll be able to make use of Go to write efficient, practical applications that use concurrency.

Mastering Concurrency in Go

When you communicate over a channel that is returned from a function, this is an example of:

When you communicate over a channel that is returned from a function, this is an example of:

The program will panic and terminate immediately.

The select statement will block the program forever.

The program will terminate after five minutes. 

What is the result of the following code? Assume that some value is sent to the `done` channel after five minutes. 
```
for { 
 select {
 case <-done: 
 return
 default: 
 } 
}
```

What is the result of the following code? Assume that some value is sent to the <code>done</code> channel after five minutes.
<pre><code>for { 
 select {
 case &lt;-done: 
 return
 default: 
 } 
}
</code></pre>

It is not possible to send a channel over a channel. 

It is not possible to send a channel over a channel.

What do we achieve by sending a channel over a channel? 

What do we achieve by sending a channel over a channel?

The best practice is when the receiver closes the channel and signals the sender that it will not be accepting any further input.


The best practice is when the receiver closes the channel and signals the sender that it will not be accepting any further input.

Test your learning and answer the following questions about concurrency patterns.  

Introduction to Concurrency

Building Blocks of Concurrency in Go

Exam I on Mastering Concurrency in Go

Basic Concurrency Patterns in Go

Exam II on Mastering Concurrency in Go

Quiz on Concurrency Patterns