Redowan's Reflections — Page 2

Four of the five steps in every unary RPC handler are wire plumbing. Pin the service function signature and they fit in one generic adapter per transport.

A Go closure holds a live reference to whatever it captures, not a snapshot. Real examples of where this trips people up, and how to keep it boring.

Notes on Go's newly accepted uuid proposal and the tradeoffs behind the API.

A quick tour of Go struct tags: how different libraries use them, how you read them at runtime with reflection, and how other tools read them at build time instead.

Translating errors at layer boundaries so storage details don't leak into the handler or, worse, into client responses.

Key takeaways from Amazon's 2007 Dynamo paper.

Why logging at every layer of a service produces noise, and how to log only at the handler level while propagating context from below.

Switch, map of functions, and interface registry for dispatching in Go.

Why & backgrounds execution but doesn't stop output from flooding your terminal.

How to test unary gRPC services in Go - handler logic, interceptors, deadlines, metadata propagation, and rich error details - all in-memory with bufconn.

Decoupling business logic from storage in Go, adding transaction support without leaking SQL details, and coordinating atomic writes across multiple repositories using a unit of work.

Adding transaction support to a repository interface without leaking storage details.

Why the middleware-to-handler boundary is a special case for context values.

A simple litmus test for when to use context values in Go.

Decoupling business logic from storage with a small interface in Go.