djongo VS redis-py

This open issue has some discussion on dependency wonkiness that helped me fix mine.

To try and save on costs and because I like NoSQL databases, I wanted to put my database up on Cosmos DB. The easiest way to do this was with its MongoDB API and the Djongo backend.

If you want to go with Mongodb you should try Djongo https://www.djongomapper.com/

This was my first time using MongoDB as the database for a website which was a really great experience of using NoSQL specially MongoDB Atlas, I'm also planning to use it in my future projects. I learned about pymongo package and djongo availabe for python. I took help from How to Use Django with MongoDB document. Initially I started researching about Atlas search and how to use them using the Atlas Search Docs.

djongo

I can't wait to connect Djongo to my MangoDB

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