django-cacheops VS django-redis

Here is an example of such thing https://github.com/Suor/django-cacheops/blob/8b3a79de29b2545...

django-cacheops is a great package https://github.com/Suor/django-cacheops

Nuts, I was hoping that this was an evolution of https://github.com/Suor/django-cacheops which uses Redis to cache and invalidate ORM result sets by an abstracted representation of filter values. It works, but has a lot of magic (as is the Django way) and takes some tending-to in production.

i came across this and this i am failing to understand what is the difference between the two and which is better.

The solution I recommend is setting up the caching backend using like redis then bringing in this awesome project django-cacheops! Takes 5 minutes to set up (literally) and you’re done!

We use django cacheops with redis and its incredible!

Redis is an open-source data-structure store that can be used as a database, cache, message broker, etc. To start using Redis in your Django application, you need to first install the django-redis library. The library makes it easier to connect your Django application to Redis.

To implement caching in Django application. First, set up your Django project and application. Then install django-redis, a project by Jazzband:

django-redis

This isn't such a big deal... There are great third-party packages (i.e https://github.com/jazzband/django-redis) for whoever needs a redis cache backend in a project.

Myself, I just use good ol' memcached for all my caching needs (https://docs.djangoproject.com/en/3.2/topics/cache/#memcache...). It is rock solid and has never failed me till now!

If your example of the counter is accurate for what you want to do, it might be faster using django-redis as your cache backend and using the incr method (which adds one to a given cache key). Repeatedly inserting and deleting database records is much slower than cache operations like that would be. Or is there a way you can avoid deleting database records, and modify existing values?