Architecture Guidance
summary
Practical checklist for database reliability using Go: build single static binaries for easy distro, exploit goroutines to spin thousands of writers for load testing, and prefer existing tools over reinventing (lost two months reimplementing a Microsoft ETL). Use observability stacks like Honeycomb and Veneur/StatsD, manage schema with golang-migrate / go-cqlx migrations, orchestrate ETL pipelines with Pachyderm or Reflow, and run restic backups with automatic restore verification so backups actually prove they work.
AI-written summary · about
chapters (11)
- 0:00Introduction and personal story
- 1:21Why database reliability matters
- 2:23Why Go excels for database work
- 5:56Avoiding reinventing the wheel
- 7:22Observability and monitoring tools
- 14:11Data schema migration practices
- 18:09ETL and data pipelines
- 24:39Database backups with Rustic
- 27:10Database drivers in Go
- 30:20CLI tools and Go trio
- 34:14Building starter kits and Twitch
related talks
39mBuilding Production Applications Using Go
43mWhen it all GOes right
49mWhen it all GOes right
32mA Journey to Postgres Productivity with Go
47mA Journey to Postgres Productivity with Go
20mWriting High Performance Databases in Go
37mBuilding Database Applications with Database/SQL
35mPainless Data Storage with MongoDB and Go