Critical - Cache subscribers listening to the same channels. about redis-oplog HOT 3 CLOSED

Also, remember the same message can be send over multiple channels, right?
So, depending on the use case and how heavy parsing the message actually is, it might make sense to give each message a unique ID and keep a small LIFO cache with parsed messages, with a look-up table/hash for the unique ID. So if you have a collection myCollection and an object {_id:'foo',prop:value} which you send over 2 channels collection::* and collection::foo that both has subscribers on the same server, you give the message a unique id when you send it and parse it only once on the receiving end. Then again, maybe this might be a micro optimization not really worth it.

However, I do think giving each message a unique ID if you send it over multiple channels might have other useful purposes.

from redis-oplog.

Assuming the redis cacher is done, and we don't usually send the message to more than 2-3 channels. When you work with 'channel' or 'namespace' it won't push it to the main collection channel. You could do that by doing:

// on an update/remove for example:
channels: ['customChannel', 'collectionName']
// will push to 3 channels
'customChannel', 'collectionName', 'collectionName::id'

Problem is, how do I give that unique id ? Redis accepts a channel and a string when publishing to it, I will still need to deserialize it in order to get the id somehow

from redis-oplog.

done.

from redis-oplog.