When I came from the very dynamic world of ruby, my first approach to designing HTTP clients in go was to think about mocking similar to what I was used to in Ruby. …
When I started picking up the go language years ago, things that stood out to me immediately were the io and net/http packages. Both of those packages were extremely well done and minimal in the amount of interfaces they exposed to the user.
What I love about net/http
The two things which stand out for…
When I mention dependency injection to folks who have Java or .NET backgrounds it usually invokes a few sets of questions — to which my usual response is:
It’s likely not as sophisticated as what you’re thinking — and it doesn’t have to be!
One of the most prevalent patterns when managing the lifecycle of goroutines in Go is to have a done channel. Here’s a quick example showing this in action:
done := make(chan struct{})for {
select {
case <-done:
return
case job := <-jobs:
// execute job
}
}
