Performance
-
context.Context is not a cache
A team I consulted with had stuffed request-scoped configuration into context values and it was slowly eating their tail latencies
-
Why I stopped reaching for sync.Map
sync.Map looks like a drop-in replacement for a map with a mutex, but for most workloads it's slower and harder to reason about