go-cache
GCache
| go-cache | GCache | |
|---|---|---|
| 8 | - | |
| 8,164 | 2,629 | |
| - | 0.8% | |
| 0.0 | 0.0 | |
| about 1 year ago | 11 months ago | |
| Go | Go | |
| MIT License | MIT License |
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.
go-cache
-
My first package in go. An in-memory cache package useful when creating multiple instances of the cache
Why I am creating this package? There is an already existing memory cache package which creates (One Janitor for One Cache) So I am running into issues where many go routines are running in our use cases causing the application to crash due to some memory leakage in the library itself or maybe multiple timers running at same time casuing the issue. Also this is a very popular github library but just doesn't fits when I am creating many cache instances. So thought about creating one package by myself.
-
VCache vs Go-Cache
I wrote a new library called VCache (https://github.com/microup/vcache). VCahce differs from go-cache (https://github.com/patrickmn/go-cache) by using a key of type "any" instead of a key of type "string". I compared the performance of both libraries on the main operations: Add, Get, and Delete.
-
Better Cache - A Lightning Fast Caching System with Full Text Search
https://github.com/patrickmn/go-cache is a well known one. My cache module is for it's fast full text search thus I recommend only using mine if u are using a pre-set cache.
-
go-cache VS ccache - a user suggested alternative
2 projects | 2 Apr 2022
-
Implement an in-memory cache in Golang
github.com - patrickmn/go-cache
-
Log4j RCE Found
> when they went a year without a release.
Cause these libraries depend on other libraries that are probably extremely out of date at that point and have their own security vulnerabilities.
An example of a project that hasn't been dismissed as "abandoned", is https://github.com/patrickmn/go-cache because it explicitly doesnt have dependencies.
So yeah, if you have a semi-complex library, a year without a release is abandoned.
-
Cache locally using text file
implementing runtime cache using map seems doable, i may just learn from github.com/patrickmn/go-cache but i dont understand what does it mean cache locally using text file. does it mean I have to:
-
In-memory caching solutions
Though pretty simple but have a look at https://github.com/patrickmn/go-cache
GCache
We haven't tracked posts mentioning GCache yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
BigCache - Efficient cache for gigabytes of data written in Go.
badger - Fast key-value DB in Go.
cache2go - Concurrency-safe Go caching library with expiration capabilities and access counters
groupcache - groupcache is a caching and cache-filling library, intended as a replacement for memcached in many cases.
noms - The versioned, forkable, syncable database
fastcache - Fast thread-safe inmemory cache for big number of entries in Go. Minimizes GC overhead
polluter - The easiest solution to seed database with Go
go-memdb - Golang in-memory database built on immutable radix trees
goavro - Goavro is a library that encodes and decodes Avro data.
goose
bcache - Eventually consistent distributed in-memory cache Go library