xingbowang

Hi Madelyn, Thanks for the feedback. Regarding to your 2 points. 1. Could we add additional hooks to support existing modules? The opt-in concern can be mitigated by having additional...

I see. I agree stage uncommitted operations is another option. It is very easy to implement for hash table. You can perform additional lookup on the staged changes before perform...

I agree it could always fall back to key copy. However, as you previously mentioned, large key copy is extremely expensive, both in terms of memory and CPU. If we...

Hi Oran: Thanks for the feedback. I agree with the concern of the complexity. As far as I understand, the feature is optional and should not incur any performance impact...

Could you elaborate more on the use case of this feature? Is it focusing on caching or durable data store? What are the acceptable behaviors during failure?

Hi [mbfdias](https://github.com/mbfdias), Thank you for providing these details. I think this is a great start. I agree that last writer win is a good way to resolve conflict, which happens...

This is exactly what I have in my mind. I am from AWS ElastiCache/MemoryDB team. I can see this works for some of the customers, but not sure whether there...

From technical perspective, there are 2 major challenges. 1. Support LWW semantic on existing data structures. 2. Update Replication logic to allow multiple replication stream on primary node, and replicate...