Not sure if I understand kv watch right?
Not sure if I understand kv watch right, is like named queues? o more like a reliable Broadcast channel?
5 Replies
I wasn't able to find the answer to your question in the official Deno documentation. However, based on your description, it seems like you're referring to a feature or concept related to key-value (kv) watching, which might be about observing changes to a key-value store.
In general, a "watch" mechanism on a key-value store could be similar to a subscription model where changes to a specific key or set of keys are broadcast to subscribers, which could be likened to a reliable broadcast channel. Named queues, on the other hand, typically refer to a messaging pattern where messages are sent to specific queues identified by names, and consumers process messages from these queues.
Without specific context or code, it's difficult to provide a precise answer. The advice given here is not based on the Deno documentation, so please double-check the accuracy of this advice and consider looking into the specific implementation or library documentation that you are using for a more accurate description of "kv watch" in your context.
Think
Real-Time mutation events. Whenever one of the keys is mutated, an event will be fired to the client.But for example if two isolates are running my app with the watch what does that mean?
- it will behave like a queue only one will get the value?
- Both will get the value
Both will get the value
I see now thanks