One of the primary strengths of Go programming language is a built-in first-class support for concurrency. Go is designed with concurrency in mind, backed by solid mathematical theory, and has incredibly good tooling for testing and developing concurrent software.
The ease of creating complex concurrent constructs and pipelines in Go raises a new set of questions: How do we teach concurrency? How do we master the skill of building concurrent pipelines? How do we represent concurrent algorithms? And how do we share increasingly complex concurrency models?
Ivan Daniluk offers a completely new approach to understanding and representing concurrency by visualizing it in 3D space. This new approach allows you to see what’s happening inside the real code—from a simple “Hello, World” to real production-level high-loaded servers. It leverages the power of open source technologies, such as Go and WebGL, to help you understand the complex but astonishing world of modern concurrent software. You’ll learn Go concurrency basics as Ivan covers the main concepts and approaches and explore common concurrency patterns and ways to build complex pipelines. . .and you’ll do it all in 3D.
Ivan Daniluk is a senior software engineer at Typeform. Ivan has more than a decade of experience in writing networking software for security market. He’s an active member of the Go community, a conference speaker (most recently at GopherCon 2016), the host of the GolangShow podcast, and organizer of Golang meetups, the author of numerous articles about Go, and the author of a few popular projects for Gophers. Ivan enjoys helping people to learn about Go and programming and is highly interested in neural networks, artificial intelligence, neuroscience, visualizations, and new approaches to education in general. His hobbies include figure skating, the Argentine tango, yachting, and astronomy.
©2016, O’Reilly UK Ltd • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com