Closed mpgxvii closed 5 months ago
other alternatives:
Spring Cache
: then we can use CacheManager
to evict values (on memory limits). Spring Cache annotations are also compatible completely with Hazelcast
so no migration needed if we move to hazelcast
in the future. See more here.This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@mpgxvii is this fixed with #432 ?
Fixed in #432
Is your feature request related to a problem? Please describe. Following #247, it would be good to cache Github responses to improve response times, avoid the rate limits, and reduce unnecessary repeated calls.
Describe the solution you'd like As suggested by @blootsvoets and @yatharthranjan, we can use the
CachedMap
impl and anExpiringMap
implementation for this. Also, taking into account the maximum memory usage.Describe alternatives you've considered
Hazelcast
for caching.Priority 5
Difficulty 6
Additional context Supports #247