←back to thread

The Evolution of Caching Libraries in Go

(maypok86.github.io)
127 points maypok86 | 4 comments | 29 Jun 25 17:07 UTC | HN request time: 1.274s | source
Show context
regecks ◴[02 Jul 25 19:47 UTC] No.44448030[source]▶
We’re looking for a distributed Go cache.

We don’t want to round trip to a network endpoint in the ideal path, but we run multiple instances of our monolith and we want a shared cache tier for efficiency.

Any architecture/library recommendations?

replies(8): >>44448526 #>>44448621 #>>44449247 #>>44449260 #>>44449523 #>>44450156 #>>44450474 #>>44450952 #
1. awenix ◴[02 Jul 25 20:34 UTC] No.44448526[source]▶
groupcache[https://github.com/golang/groupcache] has been around for some time now.
replies(3): >>44450137 #>>44453120 #>>44457488 #
2. pstuart ◴[02 Jul 25 23:58 UTC] No.44450137[source]▶
It's very limited in scope, but if it solves your needs it would be the way to go.
3. mrweasel ◴[03 Jul 25 09:12 UTC] No.44453120[source]▶
I'm insanely fascinated by Groupcache. It's such a cool idea.
4. HALtheWise ◴[03 Jul 25 17:46 UTC] No.44457488[source]▶
The original groupcache is basically unmaintained, but there's at least two forks that have carried on active development and support additional nice features (like eviction), and should probably be preferred for most projects.

https://github.com/groupcache/groupcache-go