groupcache VS InfluxDB

As shown in the title, DREAMEMO is a distributed cache with out-of-the-box, high-scalability, modular-design features.The groupcache implementation is referenced, and re-structured, specific module differentiation is as follows:

I remember one of the first real-world uses of Go being the groupcache package: https://github.com/golang/groupcache (to serve Chrome downloads, IIRC?)

> comes with a cache filling mechanism. Whereas memcached just says "Sorry, cache miss", often resulting in a thundering herd of database (or whatever) loads from an unbounded number of clients (which has resulted in several fun outages), groupcache coordinates cache fills such that only one load in one process of an entire replicated set of processes populates the cache, then multiplexes the loaded value to all callers.

I read that group cache (https://github.com/golang/groupcache) can be used to sync servers around a key.

I've not tried this myself, but I've seen it suggested to use groupcache (https://github.com/golang/groupcache) to sync your servers.

https://github.com/golang/groupcache is managing distributed caching that addresses thundering herd problem of memcache.

I really enjoyed google's https://github.com/golang/groupcache. Learned both about the language, and quality network application design

golang/groupcache (Go): groupcache is a caching and cache-filling library, intended as a replacement for memcached in many cases.

Scalable Realtime Datastore: The piece examines a scalable datastore specifically created for metrics events and real-time analytics. (2013-09-26, shares: 26787.0)

How does one upgrade from v2 beta to the latest v2? The docs for doing that seem to no longer exist https://github.com/influxdata/influxdb/issues/24393

And InfluxDB Github commit history histogram is telling its story https://github.com/influxdata/influxdb/graphs/contributors

We have 40+ InfluxDB servers (for iot sensor data) but I think in couple of years we will move to TimescaleDB. InfluxDB problem is their company InfluxData that has pivoted away from InfluxDB after v2 release and tried their Rust thing (IOx) and now is promoting their Telegraf. For me this is a sign of no clear vision from company. I can not trust my database to company that will probably abandon InfluxDB in couple of year. Just look commit histogram https://github.com/influxdata/influxdb/graphs/contributors After their released InfluxDB is run on skeleton crew. Also see https://news.ycombinator.com/item?id=23906592

InfluxDB