Session data will be stored directly in your cache. Once your cache is configured, you’ve got two choices for how to store data in To use another cache, set SESSION_CACHE_ALIAS to the If you have multiple caches defined in CACHES, Django will use theĭefault cache. NOT multi-process safe, therefore probably not a good choice for production Additionally, the local-memory cache backend is Sessions directly instead of sending everything through the file orĭatabase cache backends.
The local-memory cache backend doesn’t retain data longĮnough to be a good choice, and it’ll be faster to use file or database You should only use cache-based sessions if you’re using the MemcachedĬache backend.
