Code Reviews in Go: Top 5 Misses
summary
Teams that run a Go backend for microservices (Kafka-based, ~12 services) say they scale from thousands to almost a million users in weeks and learn concrete lessons: wrap and classify errors instead of returning naked errors, prefer unit tests + interfaces/mocks to reduce slow integration tests, cap async work with worker pools or split deployments when go routines explode pod CPU, and watch for nil pointer bugs that caused production losses (one incident sells ~70 items). Also use linters in CI and 100x traffic–tested patterns.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:37Overview
- 1:24Introductions
- 3:03Dapper Labs
- 4:25NFT Boom
- 7:16Error Handling
- 13:28Go routines
- 16:58nil pointers
- 20:28interfaces and testing
related talks
45mGo, Microservices and all the joy!
15mDo's and Dont's moving to Golang Microservice Architecture
23mRefactoring Go in Large Codebases
34mAdvanced Testing Techniques in Go
28m"Common tips & mistakes" in Go — and How to Fix Them
47mUsing Go in DevOps
46mSimplifying Scalable Cloud Application Development with Go
37mThe Need For Speed: Scaling Go Microservices - Artur Kondas