[redis-db] Is it good option for A chat app with a goal of 5 thousand users and eventually upto 15 thousand users

[Muhammad Ali Rafique]

we have around 5 k users now and eventually plan to have around 15k to 20k
users with an average of 500 messages per user per month.
We have message attachments and we can tag other users.
What should be our structure.

[h***@gmail.com]

Redis holds all its data in RAM. All of it, not just part of it. Redis
can make safety backups (called snapshot files, or RDB or AOF files) to
disk, but those are for recovery from a crash. Redis does not use disk to
store or serve its data, all data is stored/served from RAM.

If your chat system can grow to 15k-20k users and still keep all messages
and attachments in RAM, then Redis may be a good choice for you. If all
that data won't fit into the RAM you have available, then you would have to
create a hybrid storage system where the small parts (perhaps messages) are
kept in Redis in RAM and the large parts (perhaps attachments) are kept
outside of Redis on disk. Or choose another back-end data store that uses
both RAM and disk.

Under Redis what should your data structures be? That depends on a lot of
factors that are unique to your chat service. One of the Redis tutorials
creates a simple Twitter-like service in order to show several types of
Redis data structures, and that might be a good start for you:
https://redis.io/topics/twitter-clone


On Wednesday, November 14, 2018 at 5:01:14 AM UTC-8, Muhammad Ali Rafique

Post by Muhammad Ali Rafique
we have around 5 k users now and eventually plan to have around 15k to 20k
users with an average of 500 messages per user per month.
We have message attachments and we can tag other users.
What should be our structure.