🔧(backend) configure RedisCache in production settings
In development, sessions are saved in local memory. It's working well, however it doesn't adapt to a kubernetized setup. Several pods need to access the current sessions, which need to be stored in a single source of truth. With a local memory cache, pods cannot read session saved in other pods. We end up returning 401 errors, because we cannot authenticate the user. I preferred setting up a proper cache than storing sessions in database, because in the long run it would be a performance bottleneck. Cache will decrease data access latency when reading current sessions. I added a Redis cache backend to the production settings. Sessions would be persisted to Redis. In K8s, a Redis operator will make sure the cached data are not lost. Two new dependencies were added, redis and django-redis. I followed the installation guide of django-redis dependency. These setting were tested deploying the app to a local K8s cluster.
This commit is contained in:
@@ -32,6 +32,8 @@ dependencies = [
|
||||
"django-cors-headers==4.3.1",
|
||||
"django-countries==7.5.1",
|
||||
"django-parler==2.3",
|
||||
"redis==5.0.3",
|
||||
"django-redis==5.4.0",
|
||||
"django-storages==1.14.2",
|
||||
"django-timezone-field>=5.1",
|
||||
"django==5.0.3",
|
||||
|
||||
Reference in New Issue
Block a user