←back to thread

The Evolution of Caching Libraries in Go

(maypok86.github.io)
127 points maypok86 | 1 comments | 29 Jun 25 17:07 UTC | HN request time: 0s | 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. mbreese ◴[03 Jul 25 02:08 UTC] No.44450952[source]▶
Could you add a bit more to the “distributed cache” concept without a “network endpoint”? Would this mean running multiple processes of the same binary with a shared memory cache on a single system?

If so, that’s not how I’d normally think of a distributed cache. When I think of a distributed cache, I’m thinking of multiple instances, likely (but not necessarily) running on multiple nodes. So, I’m having a bit of a disconnect…