Go From Dev to Prod
summary
Covers concrete steps: use structured logs with file/line and request IDs, send them to stdout/stderr and use levels to avoid spam; vendor dependencies and commit vendor/ so CI and production build the exact same binary; build statically and set version via -ldflags so deployments report which release produced errors; benchmark and profile (example: Sprintf can be faster than Sprint on one test), prefer minimal container bases (scratch/Alpine), and use monitoring like Prometheus (pull) or snap (push).
AI-written summary · about
chapters (7)
- 0:00Start
- 7:17Dependency management in Go
- 17:01Black box testing
- 18:51Documentation testing
- 23:05Benchmarking and profiline
- 27:20Tracing
- 28:23Monitoring
related talks
19mThink Prod Up Front: Shifting Left on Production Excellence
16mSimplifying the Journey of Your Containerized Application from Dev to Production
45mDeploying to production with confidence
46mContinuous delivery antipatterns
28mHow to ship apps better, faster, stronger
40mAvoiding release paralysis
46mPracticalities of Productionizing Distributed Systems
46mSix small steps towards continuous delivery