Go + Microservices = Go Kit
summary
Argues microservices mainly solve organizational—not technical—problems and create many technical costs, then presents Go kit as a pragmatic toolkit that reduces that pain by enforcing no global state, explicit interfaces, and endpoints and middleware composition. Shows concrete patterns: endpoint constructors, service middlewares, HTTP transport adapters, Prometheus histograms, and Zipkin support via a tracing middleware. Claims dozens of operational concerns multiply across services (mentions a 40‑item checklist), and demonstrates a working, composable stack that compiles and runs.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:53Outline
- 1:33Microservice?
- 3:00Operations
- 3:42Architecture
- 4:47Did you mean.
- 6:12Problem solved
- 6:56Problems caused
- 10:47The pitch
- 11:18NOT a framework
- 12:00Compare to
- 13:59Naive implementation
- 17:23Mixed concerns
- 17:44Separating concerns
- 19:33Profile service endpoints
- 20:20Endpoint middleware
- 20:52Logging middleware
- 23:09Service concerns
- 24:55HTTP transport
- 27:04Supported transports
- 30:19Microservices are a pain in the ass
related talks
39mGo + Microservices = Go Kit
01h 01mGo Kit A Toolkit for Microservices
18mA case for microservices
31mBuilding a microservices architecture with Go
45mGo, Microservices and all the joy!
47mimport Golang; struct microservices
38mMicroservices in Go using Micro
43mHow to Sell Microservices: A Step-by-Step Plan for Developers