Good Go services make their dependencies visible.

In Go Time episode 322, Mat Ryer discusses how his HTTP-service conventions evolved over years of practice. One useful point is making dependencies explicit in constructors: tests reveal what a handler actually needs, instead of discovering hidden dependencies through a shared server object. The episode also covers routing, errors, and testing.

Go Time · Changelog · Jul 9, 2024

Why it matters

A practical companion when shaping service boundaries and deciding what a Go handler should receive explicitly.

More context

The discussion of constructor dependencies starts around 06:25. The testing chapter begins at 46:49. Use the episode’s transcript and chapter navigation to jump to the relevant discussion rather than treating the whole interview as required reading.

Keep in mind

These are the speakers’ experience-based preferences, not universal rules for every Go codebase.

Transcript read