Scaling Sustainable Innovation through Team Autonomy
summary
A small team of one product owner and four engineers builds a media platform that handles 15 million assets a day, serves peaks of 20,000 requests/sec at ~25 ms 90th percentile and emits over a billion events/month. The stack uses Go, GitLab CI/CD, Kubernetes on Google Cloud, a mono-repo with onion architecture, tracing/metrics/logs and GRPC client-side load balancing. Automated conventional commits + semantic versioning drive build/versioning; the system autos-scales for spiky loads and reduces operational cognitive load so the team can reliably ship and take breaks.
AI-written summary · about
chapters (7)
- 0:00Start
- 25:13conventional commit
- 25:47semantic versioning
- 41:57mico service design patterns
- 45:08http2 load balancing
- 47:40code generation
- 49:23secu application resilience
related talks
48mDevops@Scale
59mMove Fast But Don't Break Things
28mRefactoring Your Team For Fun and Profit
47mScaling Your Engineering System
28mFrom Startup to Scale Up: How to Scale Engineering teams
45mFrom 5 to 100 in Product Development team in just 5 years
51mTech-enabled Network of Teams
28mOpen Source at Scale Building Operation in a large company