We use it primarily for real-time applications. In our web application, we added a feature where hundreds of people could play a quiz in real time. Instead of using traditional databases like SQL, we implemented Redis to make everything happen in real time – all those quick calculations, data hashing for easy retrieval, and so on. It was a live quiz feature, so Redis helped a lot. I also use Redis for caching and similar general use cases.
In our company, Redis is used for read operations. When we receive data from a user via the Read API, we cache the response for two or three minutes to minimize API calls to the database and preserve resources within the DB. This practice also helps prevent bot-triggered dummy requests to the DB.
It was a classic caching use case. In my previous company, we were running MongoDB on the cloud, and we were running Redis for caching. We were just starting, so the data size was pretty small there.
We use it primarily for real-time applications. In our web application, we added a feature where hundreds of people could play a quiz in real time. Instead of using traditional databases like SQL, we implemented Redis to make everything happen in real time – all those quick calculations, data hashing for easy retrieval, and so on. It was a live quiz feature, so Redis helped a lot. I also use Redis for caching and similar general use cases.
Sometimes, Redis is used as a cache and sometimes as the main database.
I use the solution for saving user sessions and user data for different applications.
In our company, Redis is used for read operations. When we receive data from a user via the Read API, we cache the response for two or three minutes to minimize API calls to the database and preserve resources within the DB. This practice also helps prevent bot-triggered dummy requests to the DB.
It was a classic caching use case. In my previous company, we were running MongoDB on the cloud, and we were running Redis for caching. We were just starting, so the data size was pretty small there.