Concurrency is one of the signature features of Go, one of the things that even non-Go developers have heard about. However, just because Go makes it easy to launch concurrent processes, that doesn’t mean that it’s easy to use concurrency properly. In this talk, Jon Bodner covers the basics of concurrency, when to use it, and some of the patterns to follow when you need it. We’ll also take a quick look at mutexes, when they are appropriate, and their limitations.
Jon Bodner has been a software engineer, lead developer and architect for over 20 years. In that time, he has worked on software across many fields, including education, finance, commerce, healthcare, law, government, and internet infrastructure.
Jon is a Distinguished Engineer at Capital One, where he has contributed to their development and testing workflow, developed patented techniques for web payment page detection and population, and co-authored tools for finding and managing software development issues.
Jon is a frequent speaker at Go conferences, and his blog posts on Go and software engineering have been viewed more than 300,000 times. He is the creator of the Proteus data access library ([ Ссылка ]) and co-developer of checks-out, a fork of the LGTM project ([ Ссылка ]).
Show notes and resources may be found in our Github repository:
[ Ссылка ]
SUBSCRIBE to our YouTube channel:
[ Ссылка ]
FOLLOW us on Twitter:
[ Ссылка ]
#GoLang #Concurrency #LearningGo
