https://github.com/sonirico/mecachis
LRU, LFU, LFRU caches implementation, 缓存实现
https://github.com/sonirico/mecachis
cache lfu lrfu lru memory-cache
Last synced: 10 months ago
JSON representation
LRU, LFU, LFRU caches implementation, 缓存实现
- Host: GitHub
- URL: https://github.com/sonirico/mecachis
- Owner: sonirico
- Created: 2019-12-07T11:17:52.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2021-02-09T22:45:58.000Z (about 5 years ago)
- Last Synced: 2025-03-31T09:04:53.100Z (12 months ago)
- Topics: cache, lfu, lrfu, lru, memory-cache
- Language: Go
- Homepage:
- Size: 137 KB
- Stars: 8
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
## Mecachis
- Is your system running out of resources?
- Are your services unable to scale?
- Do you think that a good and clean architecture seems like too much?
- Is your API slow as hell because it does more than it should?
If you have answered all those questions with a "yes", fear no longer. This
brand-new package aims to someday provide those extra layers of
_cachabstraction_ and indirection that your application needs. Remember: You
can install a cache in the frontend, in front of a web server or in between
any two services that need to communicate with each other. That way, no
one would ever know where the source of truth is but yeah, the app
runs smoothly.
Now, jokes apart, this is just another academic repo to learn. This
time I'm into caches and the wide range of strategies implemented out
there to adapt caching to a wider range of scenarios. What I would
like to achieve with this repo is gaining deeper knowledge on data
structures and algorithms. Beyond that, it would be even nicer if:
- More than 5 strategies are implemented [3/5]
- [x] LRU
- [x] LFU
- [x] LFRU
- Caches are distributed over the network
- Any kind of background persistence is achieved
## Credits
### Cache eviction algorithms
Buf of course, algorithms implemented here are not of my invention, but slightly modified
to my particular needs and influenced by my knowledge state, though. I was heavily inspired
by [this wikipedia entry](https://en.wikipedia.org/wiki/Cache_replacement_policies) about cache
eviction algos.
**External links and references**
- LFRU: M. Bilal and S. -G. Kang, "A Cache Management Scheme for Efficient Content Eviction and Replication in Cache Networks," in IEEE Access, vol. 5, pp. 1692-1701, 2017, doi: 10.1109/ACCESS.2017.2669344. **Paper**: https://arxiv.org/ftp/arxiv/papers/1702/1702.04078.pdf **Patent**: https://patentimages.storage.googleapis.com/60/c5/34/c94ab8b27e2f9d/US10819823.pdf