dotnetcore / dotnetcore/EasyCaching
[EasyCachingAble] is suspectible for cache stampede problem?
Open
- Dominant language
- C#
- Stars
- 2.1k
- Forks
- 336
- PR merge metrics
- No merged PRs in 30d
Description
Seems to me like using EasyCachingAble attribute for cache isn't protected against cache stampede problem where multiple calls at nearly the same time before the cache is created are causing multiple cache refreshes. One solution would be to lock cache refresh entry with semaphore slim (Locking in https://en.wikipedia.org/wiki/Cache_stampede)
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.