django-redis VS redis-py

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?

My jaw dropped when I saw the postmortem — it was exactly the same bug concept, just in a different library! A reminder that hard things often transcend particular languages and libraries. And boy, is this a hard bug. It sits at the intersection of caching, shared resource management, and state corruption — infamously tricky problem spaces.

Oof https://github.com/redis/redis-py/issues/2665 It seems it’s not fully patched.

There is a 1 year old open bug which is almost very similar to OpenAI's issue, which was autclosed: https://github.com/redis/redis-py/issues/2028

redis

I used Juggernaut, but it seems to be not working with redis-py in current version, and Juggernaut has been deprecated recently.

https://github.com/andymccurdy/redis-py https://github.com/aio-libs/aioredis