When the “Go”ing Gets Tough: Relieving Pressure on a Budget
summary
An internal Go library adds a secondary queue/consumer and a resource watcher to reroute noncritical messages during spikes so the database stops getting overwhelmed. It integrates with gRPC, Rabbit MQ and CFKA, runs as defaults for 50–60 services, and sends alerts over channels to trigger interval/backoff/block throttlers (plus an extra strategy) that delay but do not drop messages. Demos show prioritized traffic flows, reduced DB load, and backwards-compatible, testable interfaces.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 3:17Problem and solution overview
- 6:08Architecture and flow
- 14:17Throttling strategies
- 17:56Resource manager and setup
- 19:41Design decisions and lessons learned
- 24:45Conclusion and takeaways
related talks
28mManaging and Scaling Real Time Data Pipelines using Go
04mHandling slow requests in your Go web server
43mLet's Go asynchronous
42mLevel-Up Real-time Go Applications with Ringbuffers
39mMigrating a Mission Critical Service to Go
31mBuilding a microservices architecture with Go
30mHigh Performance Systems in Go
54mComplex Concurrency Patterns with Go