gokv
groupcache
Our great sponsors
| gokv | groupcache | |
|---|---|---|
| 1 | 12 | |
| 666 | 12,724 | |
| - | 0.7% | |
| 8.7 | 0.0 | |
| 6 days ago | 5 months ago | |
| Go | Go | |
| Mozilla Public License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gokv
-
Map of Golang Key Value Engines
Really great overview!
I've been tracking some of them for a while as part of evaluating which ones to add to my key-value abstraction library gokv [1], but others only noticed recently. It's really interesting that there's no single most popular implementation, but new ones emerging and gaining popularity regularly.
[1] https://github.com/philippgille/gokv
groupcache
- [imcache] A generic in-memory cache Go library. Feedback appreciated.
-
DREAMEMO: An out-of-the-box, high-scalability, modular-design distributed cache
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:
-
Sourcehut will blacklist the Go module mirror
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.
-
Distributed fault-tolerant persistent atomic counter in golang
I read that group cache (https://github.com/golang/groupcache) can be used to sync servers around a key.
-
How can you ensure all Microservices have finished their tasks?
I've not tried this myself, but I've seen it suggested to use groupcache (https://github.com/golang/groupcache) to sync your servers.
- What is for you the project who represents the best the power of Golang ?
-
go-generics-cache: An in-memory key:value store/cache library for Go Generics
https://github.com/golang/groupcache is managing distributed caching that addresses thundering herd problem of memcache.
-
How to Create HTTP Cache Service in Golang?
How it goes sometimes. Check out https://github.com/golang/groupcache and of course the AWS golang SDK.
-
Redis inside cluster
There is also groupcache, written by the same author as memcached, but better.
- Can you share some Go package that you think has high quality clean code?
What are some alternatives?
chproxy - Open-Source ClickHouse http proxy and load balancer
BigCache - Efficient cache for gigabytes of data written in Go.
jaeger - CNCF Jaeger, a Distributed Tracing Platform
go-cache - An in-memory key:value store/cache (similar to Memcached) library for Go, suitable for single-machine applications.
badger - Fast key-value DB in Go.
cache2go - Concurrency-safe Go caching library with expiration capabilities and access counters
cockroach - CockroachDB - the open source, cloud-native distributed SQL database.
rqlite - The lightweight, distributed relational database built on SQLite.
TinyGo - Go compiler for small places. Microcontrollers, WebAssembly (WASM/WASI), and command-line tools. Based on LLVM.
Tile38 - Real-time Geospatial and Geofencing
pgweb - Cross-platform client for PostgreSQL databases
ledisdb - A high performance NoSQL Database Server powered by Go