-
|
I want to know if I need to use the related issue #265 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
I've recently learned about clusterpedia and if I have time, I will be pleasured to take part in. |
Beta Was this translation helpful? Give feedback.
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.