kerground VS django-cacheops

Dramatiq or RQ are good alternatives. If you want to something really simple I haven't testing it in production try this: https://github.com/ClimenteA/kerground

Working on a task queue (more simple than RQ): https://github.com/ClimenteA/kerground

You can get away using functools cache/lru_cache. Also, for background jobs checkout https://github.com/ClimenteA/kerground

Check kerground repo here. If you feel uninspired of what side-project to pick-up next, I accept any working contributions.

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!