> The concurrency primitives are built into language and stdlibs which means when you do need synchronization, everyone does it same way. As long as you after

> The concurrency primitives are built into language and stdlibs which means when you do need synchronization, everyone does it same way. As long as you after refactor N still are staying in the happy path avoiding the numerous footguns and implicit behavior Go supplies you with. I would say if you stray outside a single thread or shared nothing fire up a Goroutine per response architecture deeply reconsider the choice of using Go. https://eng.uber.com/data-race-patterns-in-go/ https://eng.uber.com/data-race-patterns-in-go/