Does watch feature implementation strongly depend on memory-storage?

[qmloong]

I want to know if I need to use the watch feature, then do I must use the memory as a storage layer?

related issue #265

[Iceber]

For the present, yes indeed.

But we are also looking for a more general Watch implementation.

Clusterpedia actually accesses the storage component through the storage layer interface and does not care about the specific storage layer implementation, and Clusterpedia is providing a custom storage layer based on the go plugin, so that users can provide specific Watch implementations at will.

For a generic Watch implementation, my initial thought is to base it on some lightweight message queue, such as nsq, which decouples the synchronization and query components of resources.
We can discuss and push this together.

[qmloong]

I've recently learned about clusterpedia and if I have time, I will be pleasured to take part in.