Customise Session Engine to distribute session data storage

[Web Architect]

Hi,

Right now we are using the Django cache_db session engine for persistent sessions and also for some speed. Is it possible to customise this where I can store some session data in cache and some in DB? For example, I want to store all login sessions in DB and rest like some user specific data - basket etc in cache .

Looking forward to your support....

Thanks. 

[Jason]

there's an option to use redis as a session backend, which would be faster than using a regular db, even a well tuned mysql/postgres instance

https://github.com/martinrusev/django-redis-sessions

[Web Architect]

Hi Jason,

Thanks for the response. Why not use Django's cache backend and setting cache alias to be redis?

Thanks. 

[Jason]

Actually, there's nothing stopping you from using redis for cache and session cache.  

SESSION_ENGINE = 'django.contrib.sessions.backends.cache'

will use your cache to store sessions.  and if you use cached_db instead of cache, that data will persist in redis and survive restarts.

[Jason]

and redis-sessions seems to be a wrapper around with more functionality, but the lib is a little out of date.  Got confused by the latest commit in master making it seem it was under maintenance but the latest release is over a year ago.

[Web Architect]

We were actually cache_db but the sessions were consuming too much of DB. Hence, we want some sessions to be persistent in DB and some to be volatile and not stored in DB. Hence, I was looking for some way to achieve that. Like I want all login sessions to be stored in DB whereas rest in cache. 

[Jason]

https://github.com/adw0rd/django-multi-sessions

that's a non-working project but might give you some clues how to route sessions to different backends.

[Web Architect]

Thanks. This seems to be quite helpful. Will look into it.