I used redis in my project for implementing the cache mechanism. it is very fast and reliable.

Also like the redis command line (redis cli) easy to add, remove and update the value in the redis server. Review collected by and hosted on G2.com.

In redis command line when we start writing any command it will not give any suggestions or automatically fill the command like other cli tools we can use tab button it will automatically fill the remaining command. Review collected by and hosted on G2.com.

The speed and simplicity are amazing.

Easy to understand and implement.

Stores data in memory, therefore, can perform a huge number of read and write operations per second. Review collected by and hosted on G2.com.

If the system abruptly restarts, data is lost.

If we enable real-time data backup to disk in order to avoid the above issue, resource utilization skyrockets.

Also, logging makes things run slower. Review collected by and hosted on G2.com.

Redis is highly stable, and when caching the data, it increases application speed by a considerable amount. It is highly reliable, easy to set up, widely used, and beginner-friendly. The community support is good. Review collected by and hosted on G2.com.

It does not support a variety of data types, so you'll have to do the conversion while writing and reading from it. Review collected by and hosted on G2.com.

It is in a good position in terms of cache performance and usage in the market. The most ideal storage to store your keys and values. Review collected by and hosted on G2.com.

There is nothing I dislike about Redis in general. It is quite useful. There are many client leir and management tools connected by the software. Review collected by and hosted on G2.com.

too much lightweight with API interaction

support in AWS and many other clouds services

support many types of data types to match use case of many caching scenarios Review collected by and hosted on G2.com.

Single thread nature hang sometimes on many request

Not reliable for real time DB due to lack of session handling

Documentation is not proper to understand deeply Review collected by and hosted on G2.com.

I was able to easily build a key value data store using redis. Using the replication function of redis 3.0, we were able to respond effectively to failures. Redis is used for session management of applications. It is also used to centrally manage meta data. Review collected by and hosted on G2.com.

You should keep in mind that Redis's cache TTL operates in a sampling manner. If you need to process Expired Event of a large amount of data, CPU usage may increase. Review collected by and hosted on G2.com.

I use the Redis API in my python web-stack and it is one of the slickest things I have ever had the pleasure of working with. The application that I maintain, deepquill.com, needs to serve a high volume of requests while doing continuous cloud-resource tracking/management and it all has to happen asynchronously, so naturally I turned to Redis for a high speed caching solution. At the time I knew only Postgres and Redis works very differently, so I was new to the whole system. The solution I needed to implement with this database wasn't exactly trivial either, so I was prepared to spend a good amount of time slogging through source code to learn what I needed to alter to get this module to work how I wanted it to. -- To this day I have not seen a single line of it's source code -- It's all there in the documentation, written in plain English with examples and use-cases galore! Even if there were a faster and more reliable caching solution on the market (which there isn't) , I would honestly still pick Redis if only for it's thorough and accessible documentation. Review collected by and hosted on G2.com.

The only downside I could identify with this solution is that it is not really meant to store data in a persistent form. At least not by default. Redis does everything in volatile memory (which is why it can be so fast) , and while it is easy to set it up to write your data to disk from time to time (it's maybe 3 lines of code tops), it can potentially be confusing to people who come from a more traditional database and expect their data to still be there after a power cycle. The only people who would really suffer from this misunderstanding are those didn't read the manual though, so don't be one of those and you'll be fine. Just be warned: if you want Redis to record your data in a persistent form, you have to explicitly tell it to do that. Review collected by and hosted on G2.com.

Redis is best for caching, easy to set up, and easy to use. I'm still new with Redis, but I really like Redis because Redis is really helping me to cache data, I usually use Redis on Heroku or on my local machine, it's really easy to setup Redis on Heroku because you can just select from the Heroku features you need, and select the Redis features, it really helps me to deploy an app to Heroku using Redis. Review collected by and hosted on G2.com.

No, I really like Redis, I don't think that I disliked Redis Review collected by and hosted on G2.com.

Its an all in one Utility Pack that uses very little memory on startup. I have used it for storing XML hotel master data as Tables rows. While caching inventory as Key/Values and as a Broker to improve performance for the ELK stack. The distributed cache makes it even faster when using multiple data-centers across continents. Review collected by and hosted on G2.com.

It has a very old pre-compiled version for Windows. Review collected by and hosted on G2.com.

Fast read and write

Clustering and Distributing between servers

A lot of variation in data types. Review collected by and hosted on G2.com.

Single-Threaded. You won't benefit from having multi-core CPUs.

Lack of documentation; debugging can be onerous Review collected by and hosted on G2.com.