This library is written in .NET standard and provides reliability to delivering messages via Redis. By design Redis pub/sub message delivery is not reliable so it can happen that some messages can be lost due to network issues or they can be delivered more than once in case of Redis replication failure.
Great contribution, I had been looking for something like that for some time. Is there a mechanism that eliminates the message from Redis once the subscription has picked it up?
I have seen that if I publish a lot of data (10,000 users) concurrently, delays appear between the publication and the subscription. Can you think of any ideas to avoid these delays?
It seems that publishing messages in Redis cluster allocates remarkably higher CPU power compared to publishing in Redis standalone instance. It might be caused by extensive usage of CLUSTER NODES command in a Lua script, see INFO COMMANDSTATS: .