"Go Big! Go Enterprise"
summary
Capital One teams use Go to build microservices, backend‑as‑a‑service layers, data pipelines and cloud compliance tooling running on Lambda functions, containers on AWS Fargate and ECS, or EC2; they integrate streaming with Kafka and policy checks with Open Policy Agent. Measured outcomes include APIs at millisecond latencies, much higher TPS, near‑zero vulnerabilities on some teams, smaller memory footprints, faster local build/deploy cycles and noticeable cost savings and developer productivity gains.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:52Why enterprises choose Go
- 5:00Enterprise Go projects
- 7:52Backend with Go microservices
- 12:03System of record with Go Kafka
- 14:48Cloud policy enforcement in Go
- 17:12Payment abstraction in Go
- 18:57Data coordination with Go Lambdas
- 21:23Key benefits of Go in enterprise
- 22:50Capital One’s open source








