EasyCaching icon indicating copy to clipboard operation
EasyCaching copied to clipboard

Feature Request: Distributed in-memory cache using gossip protocol

Open Miggleness opened this issue 4 years ago • 5 comments

This is more of a feature request to support scenario of a horizontally-scaled application which doesn't have the liberty to use Redis.

The idea is to have cache data in-memory, but allow one instance to invalidate the cache of other instances.

A form of gossip protocol can be used to identify nodes of an application.

Miggleness avatar Sep 11 '19 10:09 Miggleness

@Miggleness Thanks for your interest in this project.

This is a great idea about the distributed in-memory cache.

But I do not have any ideas on how to implement this feature this time.

Do you have any suggestion on it? And I want to know is there are many people need this feature or not?

catcherwong avatar Sep 12 '19 09:09 catcherwong

I just started reading about it. Ill add materials here and contribute too when time permits. By the way, great job for actively supporting this project

Miggleness avatar Sep 12 '19 13:09 Miggleness

This is a great feature,may be Reference https://github.com/hhblaze/DBreeze Use RAFT Method via Raft.NET

geffzhang avatar Oct 09 '19 13:10 geffzhang

از لباس نظامی سایه روشن دیدن فرمایید.

seoshid avatar Dec 01 '20 21:12 seoshid

Siloo software https://www.siloo.ir/bazzar-for-android/ Application Android Market

mizbanii avatar Mar 04 '21 22:03 mizbanii