Go and Redis. More than a love story.
summary
Compares two Go Redis clients by implementing a simple Redis connector for each and running go test benchmarks (set/get, HGETALL, LPUSH/LRANGE) against a local single Redis instance; finds similar latency across commands but Redigo shows notably lower memory allocations in these tests, while go-redis is the official, actively maintained client with a type-safe API; results are from a MacBook-local benchmark and may differ under production concurrency.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:41Redis and Go motivation
- 4:05Go Redis library overview
- 9:23Implementing go-redis
- 10:45Redis client comparison
- 14:47Redigo implementation
- 16:26Benchmark design
- 20:28Live benchmarking
- 21:18Benchmark analysis
- 25:40Conclusion and insights
- 29:50Q&A session
related talks
33mIntroduction to Redis
24mWhen Real Time Meets Big Data & Analytics
40mBuilding a Highly Concurrent Cache in Go: A Hitchhiker's Guide
59mUsing Redis beyond caching
01h 01mMemory First An introduction to Redis
47mGo and Ruby
36mElasticSearch and Redis How and When to Use Them
27mBehind the Keys: Redis Oyster Cult