You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For reporting a list of inactive users on the mail platform, we need to be able to record user's login activity somewhere.
Redis has been chosen as the most suitable storage for this need: famous for session data use case, fast write, AOF seems reasonable for data backup (could accept a bit of data lag for user activity use case).
regarding the way of storing data structure:
the key can be something like: last-login:<username> where username is the actual user's last login info
the value: a JSON that would have the last connection date, ip and user agent registered per protocol (imap, smtp). We would use Redis JSON.SET command
cf EPIC for context
For reporting a list of inactive users on the mail platform, we need to be able to record user's login activity somewhere.
Redis has been chosen as the most suitable storage for this need: famous for session data use case, fast write, AOF seems reasonable for data backup (could accept a bit of data lag for user activity use case).
regarding the way of storing data structure:
last-login:<username>
whereusername
is the actual user's last login infoExample of the JSON value:
Maybe create a new module under tmail-backend for this, like
user-login-redis
? (can discuss the name)DoD
The text was updated successfully, but these errors were encountered: