Alexander Schepanovski

A note: we have 2 approaches here hash tag function vs router function. A second one also solves master/slave.

Looked through the patch. Working approach overall, I see 2 major issues though: 1. Non-cluster usage is completely broken in it, since `SafeRedis` and `StrictRedis` don't have additional methods of...

Nodes change check as written probably won't work. Here are my considerations: 1. `id()` of mutable object doesn't change when object is changed, so there is no point in comparing...

@Grokzen the issue with using redis cluster for cacheops is that doesn't fit this whole lot of hashslots model. The reason for this is that cacheops uses one keys refering...

@Grokzen its `queryset._cache_key()`. Can't see how this is relevant though.

@genxstylez sharding lib is a trivial part of making cacheops multi-server, the main part is choosing sharding or routing strategy. See above.

Implementing cache [key prefix](https://github.com/Suor/django-cacheops/commit/29ad33f635beeebf6a71b55ef564cb87309dd69f) was a step towards it. The idea is to use `{prefix}`es with braces and `redis-py-cluster` for sharding. Setting everything up turned up to be bigger than...

People often implement some custom solution, which is hardly generalizable, or just don't have time to clean it up and contribute. This exists and open for discussion and reference, there...

`precall_key` set to `''` means do not use it, unfortunately this doesn't play nice with redis cluster semantics. The solution could be on of: - generate two versions of `cache_thing`...

Hello @AndyHoang, thanks for your example. I think those things might be incorporated as long as it still works for single redis scenario.