Madelyn Olson

> Yeah we can achieve single-range per shard with the slot-based implementation. Consistent hashing is just for comparison. If other databases use it, they must accept the downsides that the...

Can you add some additional information about what types of workloads you are trying to support. Active/Active replication is a hard problem with a lot of tradeoffs. It would be...

> In our case, we currently use Redis to hold user session info for SSO purposes. I presume that means you are using a hash or a string? Are you...

@cjabrantes I skimmed the document quickly and don't know much about the technical details, so not sure how much it would be to implement this feature. I know that keyDB...

@mbfdias Less "not-planned" and more "need someone to implement it", which is hard given we are a community driven project.

@valkey-io/core-team I think this is straight forward enough to vote on. I believe the idea is to primarily reduce the overhead for clusterbus metadata. I suppose the alternative would be...

We had one person message it in Redis, you can see the attached link. I'm not aware of how popular it is.

> OK, I've read the Redis issue now. If we add MPUBLISH, we're expected to add SMPUBLISH next? I think this was proposed because the overhead of using the `PUBLISH`...

> > Can we just add multi-`PUBLISH channel message [ message ... ]` now, together with #557, and get it over with? We haven't needed any flags or other args...

> We can use this action to avoid implementing this: https://github.com/jidicula/clang-format-action Can we add a README for how to run this locally if we use some 3P validator. I don't...