Redis

(74)
4.4 out of 5 stars

Redis is an open source, advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists , and sets.

Work for Redis?

Learning about Redis?

We can help you find the solution that fits you best.

Find the Right Product

Redis Reviews

Ask Redis a Question
Write a Review
Filter Reviews
Filter Reviews
  • Ratings
  • Company Size
  • User Role
  • For Category
  • Industry
Ratings
Company Size
User Role
For Category
Industry
Showing 74 Redis reviews
LinkedIn Connections
Redis review by ammu P.
ammu P.
Validated Reviewer
Review Source

"Review for redis"

What do you like best?

Redis is a open source ,Scalability ,Pub sub models,Luascript,key expire,key space notifications,Memory optimization,distributing of data among multiple redis instances

Memory optimization,key expires,creating secondary indexes with redis,Pipelining concepts in redis, No lack on tutorial for a lot of use cases, storing temporarily data

What do you dislike?

Unable to store high amount of data ,We should not able to observe logs(prints) while return code in luascript that return single time only so that we are difficult to find out errors,Insert into a LIST is O(1) complexity

Recommendations to others considering the product

I would like to recommend the redis database for data replication and can save data on disk and it is very fast.Debugging Lua scripts is very easy,We can optimize the memory usage.

If considering using Redis for a project, just try it, it's easy to use and feature-rich. The community is really active and there's no lack on tutorial for a lot of use cases

What business problems are you solving with the product? What benefits have you realized?

While doing project mongo db unable to handle parallel requests so that we go with redis.Redis having low latency time so better to go with redis database.

Sign in to G2 Crowd to see what your connections have to say about Redis
Redis review by Jonathan W.
Jonathan W.
Validated Reviewer
Verified Current User
Review Source

"Great in-memory storage"

What do you like best?

What's best to appreciate about Redis is how quickly it's growing since it's first appearance and how useful and fast it is for many parts of a software implementation.

It always seemed to me like a storage option for caching or indexing, but it is way more than that. Some features are definitely to be highlighted like:

* Pub/Sub message system.

* Redis Cluster

* Expires

* Lua scripting

* Blazing fast

Are some of the things I noticed that make a difference when looking for this kind of memory storage.

What do you dislike?

I used to dislike the lack of features on Redis, but that was like 2 years ago, it has grown so quickly so fast that it's scary, the community is strongly focus on this product development.

Recommendations to others considering the product

If considering using Redis for a project, just try it, it's easy to use and feature-rich. The community is really active and there's no lack on tutorial for a lot of use cases.

What business problems are you solving with the product? What benefits have you realized?

Pretty much anything that needs to be stored and retrieved fast, like caching is a great use case for Redis. For example to store session information in web applications. Also to store large amounts of incremental and volatile data, since it can be "expired".

What Key-Value Stores solution do you use?

Thanks for letting us know!
Redis review by Lee H.
Lee H.
Validated Reviewer
Verified Current User
Review Source

"Redis as a stream of intent"

What do you like best?

Redis fits a sweet spot which is "out of band data store server". I work with a lot of CQRS/ES systems and in these systems it pays to have a persistent "out of process" view of typical data types such as hashes, lists, sets, etc.

It's fast, convenient, and the defaults make it a pleasure to use. Seeing how antirez maintains it makes it one of the go-to pieces of software that I instinctively trust based on years and years of astounding stability.

What do you dislike?

Redis has some sharp edges which only become apparent when you start to get off the beaten track. I recently suffered a few grey hairs because the algorithmic complexity of LRANGE is (S+N), where as the comment to insert into a LIST is O(1). The performance of LRANGE becomes problematic when taking the last few dozen items from the end of a very, very long list. Of course having huge lists is an anti-pattern, and it was easily solved by using the bindings Lua to implement a "fake" command which partitioned things into small lists, whilst taking care of pagination, etc.

Recommendations to others considering the product

Beware that Redis expects you to store data in the way you expect to *query* it. Take the time when designing your schema to imagine *how you want the data to look when you get it out*, and take care to store it that way.

In RDBMS you can query very flexibly to pull things out in any way you care to imagine, but you pay a penalty on inserts for this flexibility.

What business problems are you solving with the product? What benefits have you realized?

In our CQRS/ES system, the core concept is to pick the *ideal* store for reading, and writing. To embrace the asymmetry inherent in building systems to enjoy the freedom to pick the perfect data store for writing, reading, querying, etc depending on the exact use-case.

Redis' O(1) insert performance is idea. From there we have async processes that build idealised read-stores for certain types of data. Profiles are stored as JSON (on disk) ready to be delivered via our API with minimal involvement from the application servers. Things like contact lists, friendship groups and other "indexes" are also stored in redis as sets, hashes or lists. Redis solves all our data storage needs barring "static files" (for that we have a filesystem) and our "search" for which our clients usually expect something like ElasticSearch.

Redis review by Vincent C.
Vincent C.
Validated Reviewer
Review Source

"Perfect in-memory data structure storage with persistence"

What do you like best?

The Redis database is really easy to install and also easy to use. Configuration also fits into a single file.

Performances are very good and this tool allows you to scale your applications with ease.

The interesting thing with Redis when you develop web applications for instance is that you can use it for many purposes such as caching files, storing temporarily data, queueing, pub/sub system, and so many things.

Redis also allows you to choose fine-grained memory types to optimize your data storage.

One last thing, but not least, you can also write some custom Redis modules using the C language. This way, you can go further with your data storage and trigger Redis functions programmatically.

What do you dislike?

Honestly, nothing. This is a very good product at all levels.

The thing I can criticize is the security part: I actually have a token stored in the configuration file (clearly); which is not the best way to protect data.

Recommendations to others considering the product

I really recommend Redis for its simplicity and its robustness.

What business problems are you solving with the product? What benefits have you realized?

I use Redis for managing tokens that automatically expire after a defined time (3 days for instance) and also in order to manage application cache with keys.

I know that a new feature is also available now: Redis Stream in order to manage consumers for reactive applications but I haven't tested it yet.

Redis review by Nico C.
Nico C.
Validated Reviewer
Review Source

"Very quick server DataStore"

What do you like best?

Redis comes in a very light and fast environment which allowed me to run my test on an old Raspberry Pi without lags due to computation times.

What do you dislike?

There is a big lack of documentation both on official website that on online tutorial.

Moreover the event management is quite poor (but under active development).

This, in addition to the weird syntax, caused a little of problems in getting started with it.

Recommendations to others considering the product

If you are looking for a very fast datastore, Redis may be what you are looking for. Please be aware that it is so fast because it saves all (of most) of the storage directly on RAM, therefore it requires a server with a lot of primary memory in order to exploit it's full potential. This may lead to an increment of costs which should be considered.

Redis has a log file on disk with the history of all action performed which is used in case of recovery. By default this log is updated asyncronously at certain time intervals, this means that if a problem occours between two interval, it may lead to a data loss. It is configurable to update on log on each action, but this has to be bechmarked as may reduce performances.

What business problems are you solving with the product? What benefits have you realized?

I was working on a disaster-management mobile application and Redis was the datastore selected on server to manage the data because of it's impressive speed (which was a requirement in the development context).

Redis review by Frank M.
Frank M.
Validated Reviewer
Verified Current User
Review Source

"More than a database"

What do you like best?

Redis is easy to install, clean, nothing complex. The usage via CLI or drivers for programming languages - I wrote two for Google Go and Erlang/OTP - is simple too. But whats most fascinating is the fact, that it's not only a key/value store. The different types like hash, list, set, sorted set, hyper log log, and geo are great and useful. Also pub/sub and the internal Lua scripting help a lot. And last but not least is Redis extreme fast.

What do you dislike?

The transaction model is a bit different. Users have to understand it and care for it. Additionally there's no real security model, only a simple authentication via password. There's no multi-user model and no right control regarding types, keys, or key patterns. So this has to be done by the using application while the database is secure on an internal server.

The database does not work with queries on values. Keys can be queried, other indexes have to by created by using sorted sets. But that's not the typical usage of Redis, so no larger problem.

Recommendations to others considering the product

Simply try it together with the CLI and visit the web site http://redis.io to see the available commands. Most clients directly let you use these commands or provide them through own functions.

What business problems are you solving with the product? What benefits have you realized?

Mostly two types of use cases. One is the typical use as a cache, simply because it's fast and the automatic key expiration (if wanted) helps a lot. The other one is the temporary aggregation of statistical data using the different data types. For some smaller projects I'm also using it as a simple data store.

Redis review by Peter J.
Peter J.
Validated Reviewer
Verified Current User
Review Source

"My favourite Database of Alltime"

What do you like best?

Its basically a datastructure store. You have a lot of data types like lists, sets, sorted sets, hash and these can directly interface with our programming languages database.

It is and in-memory database so its extremely fast and very good for high read throughput and heavy read workloads.

It is open source and free which makes it really trustworthy. It is used by us for our job server and also as a message queue and pub sub functionality for realtime notifications. Its backup and save mechanisms are really good and is easier to use than most other databases.

Its command protocol is very easy to use and implement and very fast also. Pipeling also improves threshold and is currently the fastest database I've seen.

What do you dislike?

It doesn't have truly serializable ACID transactions . Its clustering support is still not fault tolerant. It can't be used as your primary database. Doesn't have proper query language so analytics becomes a little hard and we may need to use lua for it.

Recommendations to others considering the product

If you have a lot of reads hitting your main database then you need to get redis and that stuff man.

What business problems are you solving with the product? What benefits have you realized?

We bring gamification to the global mass. One importart feature for gamification is leaderboards and we use redis sorted sets a lot for it. We also use it for caching our sessions so that our users get an immediate response and we don't need to hit our databases for everything.

Redis review by chedi t.
chedi t.
Validated Reviewer
Verified Current User
Review Source

"redis review"

What do you like best?

Redis as a key/value network storage database gives exactly what it advertises. the In memory storage can really boost the performance of many application while relieving the developer of the headache of managing shared memory between threads or programs on the same machine or over network.

With the increasing reliability of the hardware, we are unlikely to have a server failure that will cause the loss of the data and even if that is an issue, with the persistent storage and the data replication between servers you can have a robust system that will keep your data with little to no overhead

What do you dislike?

nothing in particular, redis is a very reliable product that do one thing and do it right

Recommendations to others considering the product

Redis is a great tool for storing key value data, don't use it a relational database and adapt your software to redis and not the other way around to get the most of it.

What business problems are you solving with the product? What benefits have you realized?

We started using redis as a cache system for Django, but with passing time we started using it directly in to share data between various applications and systems.

Redis review by Josh V.
Josh V.
Validated Reviewer
Review Source

"Excellent utility"

What do you like best?

I love how simple Redis is to spin up, and I love the protocol. Everything is so fast and simple.

What do you dislike?

I haven't actually setup any highly available Redis clusters. It seems complicated enough to be a bother, which is understandable given the actual technical complexities of any clustered application. That said, based on my research, setting up a highly available Redis cluster seems significantly more straightforward than a similar arrangement with something like PostgreSQL.

Recommendations to others considering the product

Dive in head first. You'll love it. It provides immediate access to all sorts of wonderful features. It's simple to setup for development environments, for testing, and for production loads. As I mentioned previously, I've yet to setup a highly available Redis cluster personally, but the documentation suggests is straightforward enough relative to what it takes to cluster some other popular data stores.

What business problems are you solving with the product? What benefits have you realized?

Redis has made it simple to speed up several applications by not requiring certain things to be re-calculated over and over when the inputs for the calculation do not vary much. The built-in key expiration is a fabulous feature.

The PubSub features in Redis make simple work of passing messages between two or more applications. I've also used Redis as a way to synchronize resource locks across applications on the same system and across a network of servers. It's very versatile.

Redis review by Jamie C.
Jamie C.
Validated Reviewer
Verified Current User
Review Source

"Primarily used Redis for queueing jobs using Django and Celery"

What do you like best?

- Ease of setting up

- Complete and helpful CLI

- Interactive docs are VERY cool

- Detailed approach to memory management that is applicable to large systems but still useful for smaller deployments.

- Wide set of possible applications - almost endless.

- Documentation is great, despite parts that can be improved (see "What do you dislike?")

What do you dislike?

- Documentation can contain misleading information at times

- A more detailed documentation set on installation and configuration would be helpful

- Difficult to configure in multiple virtual environments, but containers can handle this separation so it's not too bad

- Query language could be improved, I find myself struggling to use it effectively, but that could just be part of the learning curve.

Recommendations to others considering the product

Truly understand the purpose of redis in your implementation. It's so easy to get caught up in newer tools (ahem, buzzwords) through word of mouth, and I often see new users working with Redis without even fully understanding why, how they benefit, or what other (sometimes more appropriate) options are available.

What business problems are you solving with the product? What benefits have you realized?

- Asynchronous task management

- Mostly realized that it was much more convenient to use redis and celery than anything else. Documentation and support is wide-ranging, and speed wasn't really a concern, so the out of the box solution worked just fine.

- Realized even more tasks that can be passed off to asynchronous workers once it was all up and running so well.

Redis review by Sean J.
Sean J.
Validated Reviewer
Verified Current User
Review Source

"Simplicity Included"

What do you like best?

Embedded Lua scripting, speed, customization, and ease of configuration. The fact that it takes less than 10 minutes to configure and spin up a perfectly working Redis instance is amazing. Compound that with high-availability provided by Sentinel and some of the other tools available to spin up a Redis "pod" and the possibilities are endless.

What do you dislike?

Lack of security. Despite the fact that a user can limit access to Redis with a simple AUTH password and limiting database access to only local networks, I feel that there could be a little bit better of a security implementation, especially considering Redis' wide adoption.

What business problems are you solving with the product? What benefits have you realized?

I found myself spending a lot of time searching for a decent SSO solution that was small, worked well with Nginx, and was quick. Eventually I gave up on the search and wrote my own and used Redis as a data store.

When I was spending time designing the session mechanism, some problems that always came up were expiration and session validation. In the sign-in process, a user is assigned a session token that maps to a hash of data in Redis. During sign-in, the SSO solution takes advantage of Redis' TTL and EXPIRE features to implement the session expiration. Because of this, the code got an extreme amount more simplistic. As far as validation goes, since it somewhat fits hand-in-hand with expiration, if the key expired or doesn't exist in Redis, the session is destroyed and the client is redirected.

With my SSO project, I really realized the true power of Redis. Its power and flexibility has drastically reduced the amount of code I had to write to achieve my goals.

Redis review by Brett J.
Brett J.
Validated Reviewer
Verified Current User
Review Source

"Infinitely configurable, scalable, high-performance"

What do you like best?

My favorite Redis "feature" is that it needs almost no configuration out of the box, while allowing many configuration options should you need it. The development team is very responsive and will fix bugs that are reported on Github.

What do you dislike?

Networking and cluster configuration is immature. Clustering only recently came out of beta, and it's not quite ready for containerization. It currently isn't possible (without a few hacks) to cluster redis instances running in docker due to it using a private IP that isn't accessible outside that docker container.

Recommendations to others considering the product

Take a look at other key-value stores before setting your heart on Redis. Redis seems to be the standard, but there are some new players on the block. There are several options that may be more worth your time if you don't need Redis to be networked, or you need it to be embedded within your application.

Where Redis really shines is synchronizing states across instances, both on the same machine, and across machines with little configuration.

What business problems are you solving with the product? What benefits have you realized?

We are experimenting with using it as a sort of backend for our authentication and authentication platform as a cookie store.

Redis is perfect for syncing data between several machines and for being a key-value store for auth tokens. It's also useful for synchronizing state between multiple machines that doesn't need to persist. I used this for load-balancing websockets between servers without requiring the user to access the same server for each request, which serves to make the system more stateless.

Redis review by Ross S.
Ross S.
Validated Reviewer
Verified Current User
Review Source

"In-memory database that feels like variables on steroids"

What do you like best?

If you are not a fan of heavy databases or any at all, Redis is the perfect one for you when you really need one.

1. In-memory database - Play with it, set variables, change them, close it whenever you feel like and nothing touches the disk unless you save explicitly. This is precisely why it is one of the fastest one around - it easily beats mysql and others in read/write cycle benchmarks.

2. Variables with timeout - Set and expire variables with a timeout, very handy for cache and other applications as the expiration is native.

3. Simple type of variables, learn in less than a day - It supports a handful number of variables like string, array and hashes, almost similar to what every programming language already has - so it feels second nature to deal with them in redis db, if the client library handles the type conversion itself. In python, redis-py does it well.

4. Batch read/write with pipelines - Run multiple commands in a single batch and return all the read operation results at once, which helps optimises the read/write operations but most importantly ensures that no other command run in parallel will run in between them.

What do you dislike?

1. No integer type - It has all those good old simple variable types, but still I miss the ability to just save some integers and get them back in the same form. Currently, you must store them as string and after getting it back, convert them back to int explicitly.

2. No array sub-operations - Arrays can be stored as such, but there is no option to change part of the list in-place, without replacing the whole one i.e. for eg. to replace the i-th value with j-th value.

3. Windows in not officially supported, only ported by MSOpenTech - As Windows doesn't enjoy official support and I am primarily a Windows user, I don't like the fact that new versions are usually not available for long time before they are ported over to Windows. Despite all that, MSOpenTech owes my respect for maintaining and porting it so well.

Recommendations to others considering the product

If you are looking for an alternative to Mysql, Redis is not it. It cant cope with large databases which can't be retained in memory.

Redis is more of a short and sweet thing that can handle relatively small number of variables with high throughput and is easy to deploy.

What business problems are you solving with the product? What benefits have you realized?

I am generally not a fan of heavy databases and didn't think I would actually need that at all, except when I needed - it was not because the data was large, but because it needed reads and writes from multiple processes running in two remote machines. I turned to Redis as I had heard that it is very simple to get started with and is really fast. And to my surprise, it really did work like a breeze.

For python projects, redis-py is the official redis client library and it mostly just maps from redis commands to methods, like get, set and hmgetall, but it also supports transactions and others.

Benefits -

The code went from supporting just one machine (variables in python) to N number of remote machines (via redis) in just one day. It became only a matter of installing redis-cli on all remote machines and reading the data off the master redis database.

Redis review by Francis A.
Francis A.
Validated Reviewer
Verified Current User
Review Source

"Storing short-lived user billing and content consumption"

What do you like best?

Simplicity, write speed, and live configuration update

What do you dislike?

The read/write synchronization can be improved. For high load realtime systems, using replication sometimes introduces lags which affects availability.

Recommendations to others considering the product

It is useful to take sometime to evaluate the data structures and choose a model that allows for fastest query times. Glob style key searches are linear and can take a while if data is too large.

What business problems are you solving with the product? What benefits have you realized?

Use case was storing realtime billing and content consumption data persisted for a week for a mobile based service. Redis enabled very fast write throughput on a large volume of streaming data. It also made modelling the realtime aspects of the system a lot simpler than anticipated, unlike an RDMS of straight forward key/value data store would have. The suite of data structures saved writing a lot of analytics code (aggregations) which translated naturally to Redis queries given how the data was written.

Redis review by Semyon P.
Semyon P.
Validated Reviewer
Verified Current User
Review Source

"Great solution for web dev"

What do you like best?

Redis is not only very fast because of its in-memory store but also could persist data on disk via snapshotting. Installation is very simple, Redis is ready out-of-the-box. You could use this store absolutely with any programming language, amount of clients and drivers is really huge. It need just a little configuration and maintenance efforts. One of its big pluses: Redis is absolutely free and open source.

What do you dislike?

Configuring a cluster may be cumbersome. Amount of clients for each modern language makes you choose between similar solutions.

Recommendations to others considering the product

Redis is absolutely necessary solution in web development and I couldn't imagine modern application without it. It has "one command" installation and you will enjoy using it.

What business problems are you solving with the product? What benefits have you realized?

We widely use Redis in web development. Our main use cases: key-value store for sessions data and fast queue for task workers.

Redis review by Josh S.
Josh S.
Validated Reviewer
Verified Current User
Review Source

"Redis scratches a lot of itches"

What do you like best?

The robust data structures that Redis offers are by far my favorite feature. It can be used as a simple key/value store like you would do with Memcached but also allows you to create hash tables to simulate more Mongo-like features as well as lists and sorted sets that can be used for queues, chat systems and leaderboards (basically anything you want sorted). Also, the option to flush to disk and have persistence is pretty awesome.

What do you dislike?

You can't really search through keys (there's a debug command for it, but not for production use) or through values. Sometimes you just want to be able to grab all the hashes that have value X and you simply can't without creating additional keys to track the mapping. This is a shortcoming compared to Mongo where you can still pull documents that contain a specific value. Also, the speed to shutdown and startup larger databases is a tad sluggish.

Recommendations to others considering the product

I wouldn't recommend it as a drop in replacement for MySQL or anything due to the limitations for searching, but for caching as well as queues and scored data (like game leaderboards) it's the only choice.

What business problems are you solving with the product? What benefits have you realized?

I use Redis for a series of things, specifically a chat system and leaderboards for tracking site activity. I have also used Redis a ton in front of MySQL to serve as a more direct index in scenarios where queries are under performing and the tables are so larger (50m+ rows) that trying to reindex means a chunk of downtime. I also use Redis for user sessions. I am also starting to migrate away from Memcached for basic key/value stores in front of MySQL.

Redis review by Timothy S.
Timothy S.
Validated Reviewer
Verified Current User
Review Source

"redis for in-memory data access"

What do you like best?

The ease of setup and usage of redis is amazing. You can just brew install redis or apt-get install or download and be up and running with a single node in minutes.

The community around redis is very strong with lots of support, examples and documentation.

Redis is an excellent database that has a ton of support clients and drivers for NodeJS, Go, Java, Scala and all the languages that we use.

What do you dislike?

Setting up clustering is a bit hard and there's not a lot of documentation on that. The process just changed, so hopefully it will get better. The enterprise version from RedisLabs is a lot easier to use.

I would like if it connected with things like Mesos and kubernetes easier.

Recommendations to others considering the product

Make sure you use the latest 64 bit version and if you can use the RedisLabs clustered version. The creator of Redis, Salvatore works for them and it's really solid.

Redis is great for caching and for real-time data access. We use it as an HTTP session cache, HTTP cache, ORM cache, temporary memory and as instead of memcache.

Redis is a great product and works great with Scala, NodeJS and Java.

What business problems are you solving with the product? What benefits have you realized?

We have solved our performance issues by using Redis instead of a RDBMS. Redis is a greatly faster than MYSQL, Postgresql or Oracle for most things we need to do.

Redis is also a great cost saver over commercial cache and in memory solutions as it is free. We just need to pay for our EC2 instances which are fairly small for this.

Redis review by Rudy P.
Rudy P.
Validated Reviewer
Review Source

"Digital Marketing"

What do you like best?

Unlike the free cache modules, Redis is a well known provider with good reputation. While I have not implemented this cache in real environment, I am confident if it will deliver as promises.

What do you dislike?

Memcache is also good and free. Our team is more familiar to Memcache.

Recommendations to others considering the product

Try other cache options, including the free before jumping to Redis so you can see the different.

What business problems are you solving with the product? What benefits have you realized?

Slowness while access database. We combined Varnish and Memcache and solved most of the first byte issue.

Redis review by Juan S.
Juan S.
Validated Reviewer
Verified Current User
Review Source

"Redis is absolutely fantastic."

What do you like best?

What I like best about Redis is that it is fast. Absolutely, blazingly fast. I primarily use it as an edge cache on my applications for data that I would not want to do a round trip to either Mongo or MySQL for and I am constantly blown away by how quick it responds. It's like memcache on steroids.

What do you dislike?

The biggest thing I dislike about redis is that without proper management one can end up with memory fragmentation issues that cause performance degradation when writing large amounts of data. Granted, I haven't run into this issue as most of what I have used Redis for is profile and product data - records ranging in size from 1kb to 10kb at the largest.

Recommendations to others considering the product

Try it, at least once - I'm sure you'll fall in love with it. If you're worried about persistency related performance degradation, a few tweaks to the kernel are all that need be done. Nothing painful!

What business problems are you solving with the product? What benefits have you realized?

On the small end, I have used Redis to considerably increase the performance of client applications that were largely bloated and did many back and forths to the database as they were architected. When the client brought me on to fix their performance issues, the first thing I did was plug Redis in as a front data cache. Additionally, I have used Redis for a personal application with ephemeral data, using it as a simple KV store for the interim results of certain steps of a long running calculation.

Redis review by Hubert L.
Hubert L.
Validated Reviewer
Verified Current User
Review Source

"Fast, easy to use, adequately featured"

What do you like best?

Great feature-set, and not bloated. Libraries for major languages.

What do you dislike?

I normally depend on 3rd party hosted solutions to reliably serve a Redis cluster.

What business problems are you solving with the product? What benefits have you realized?

High frequency key-value database. Perfect for creating a message queue from, with features that support atomic transactions.

Redis review by Riley T.
Riley T.
Validated Reviewer
Review Source

"High performance, easy to work with"

What do you like best?

Redis is very performant and easy to scale against. We ran this on a system powering thousands of light-load websites and it increased our web farm capabilities significantly. It is also very easy to wrap in a large number of software environments, ours being .NET.

What do you dislike?

Windows support is not very strong. While I think many developers would prefer to use Linux servers, often times the decision was made several years ago (and at a higher corporate management level) to use Windows; Microsoft has done a great job with lock-in once one starts using their products. Because of this I think the Redis community in general has lacked adequate focus in this area.

Recommendations to others considering the product

While the clustering support is not yet as strong as memcached, Redis has begun to focus there as is evident with Redis Cluster. Definitely look into Redis Cluster when considering Redis.

What business problems are you solving with the product? What benefits have you realized?

We need a high-performance, distributed key-value cache. We immediately realized large benefits when Redis came to our database's rescue, off-loading unnecessary requests when data was unlikely to change.

Redis review by Filipe O.
Filipe O.
Validated Reviewer
Review Source

"Lightweight and powerful key-value database."

What do you like best?

It's very easy to get started with Redis. It can store different types of values, making it fit in dfferent use cases. It's also useful to store cache and session stuff in memory.

What do you dislike?

I've heard it may turn out difficult to configure big setups for production, but I haven't been into that problem yet. So, I don't have anything to complain about it at the moment.

Recommendations to others considering the product

There are many types of databases today, and none of them is suitable to store all kinds of data. Take care when evaluating Redis isn't a good choice, because it is - perhaps your scenario isn't well suited for it only.

What business problems are you solving with the product? What benefits have you realized?

I'm using it barely to cache session data, which is one of the simplest use cases of Redis. It's very easy to setup it in any application for caching and it's very fast when running in memory. Also, it helped me remove temporary data from my main database.

Redis review by User in Higher Education
User in Higher Education
Validated Reviewer
Verified Current User
Review Source

"Excellent alternative to traditional databases when performance is necessary"

What do you like best?

Redis is an extremely fast, easy to use, and well documented data store. The best aspect of Redis is its ease of use (installing, configuring, and accessing it is a breeze).

What do you dislike?

A downside of Redis is that there is a very large number of commands available to perform all of the different manipulations (almost 200 of them at the time of writing). This allows for great flexibility but requires accessing the documentation very frequently.

Recommendations to others considering the product

Redis is when used for its intended purpose. For relational data where speed is not a key issue, a traditional SQL database is a better option. When speed is an issue and a disk-based database does not cut it, Redis can serve as a great alternative.

One thing to consider with Redis is that since it is a NoSQL data store, and since it does not enforce any schemas at all, your application code will require a lot of extra logic that would typically be abstracted away to SQL queries. You will have to perform a lot of "book keeping" to keep track of set elements, existing keys, etc. in order to use Redis effectively.

What business problems are you solving with the product? What benefits have you realized?

The problem that Redis solves best over a traditional SQL database is that its in-memory nature makes data entry and retrieval extremely fast. When latency with disk-based databases is an issue, Redis' speed can be used to mitigate this without the need for scaling or adding servers.

Redis review by Soham K.
Soham K.
Validated Reviewer
Review Source

"Using redis to build scalable web applications"

What do you like best?

Extrmely fast for its particular use case. Scales easily. Should be used for everything that it can be used for.

What do you dislike?

Can only be used for small fast temporary data. Cannot be used for storing long term data, and is limited by the RAM of the system.

Recommendations to others considering the product

Redis is a great simple and open source solution. I implore others to use it, but be aware of what Redis specializes in ,which is fast reliable storage of data that needs to be retrieved fast, and not long term storage of large data.

What business problems are you solving with the product? What benefits have you realized?

Currently building an application which manages lots of users and lots of aggregated data. Used MySQL for both data aggregation and user session storage. It was apparent that user session storage was not fast enough for our business needs. Redis greatly improved the speed and robustness of our application, since the read/write speed was much faster the MySQL

Redis review by Stewart H.
Stewart H.
Validated Reviewer
Review Source

"A Distributed Workhorse"

What do you like best?

My absolute favorite thing about this tool is its distributed, swiss army knife nature. Need a distributed job queue, distributed set, map.

What do you dislike?

The issue that I dislike the most is probably the cost that comes along with holding everything in memory. We have to use some hefty instances on AWS to yield the benefits of having certain data available at a moments notice.

Recommendations to others considering the product

I would recommend setting this software up locally to start, installing the python client for it and toying around with it. It is very easy to get started with. Just watch the instance sizing if you are using Digital Ocean, AWS, etc as it likes the memory which greatly bumps the costs up.

What business problems are you solving with the product? What benefits have you realized?

For the most part, we are storing jobs that software needs to run on it in a distributed fashion. It has been very easy to implement and easy to monitor.

Redis review by Ng Z.
Ng Z.
Validated Reviewer
Verified Current User
Review Source

"Easy to use. But too expensive. Memory limited"

What do you like best?

Very easy to use. A novice can pick it up and put to use almost immediately. Documentation very easily done

What do you dislike?

Very expensive, because of memory limitation. Not sure if the current version supports multiple instances

Recommendations to others considering the product

It's really the Swiss army knife. Documentation is a breeze to pick up. Really! Performance is as advertised.

What business problems are you solving with the product? What benefits have you realized?

I needed a database that offers very fast read and write operations. Redis delivered. Except that my needs have outgrown now

Redis review by Robinson A.
Robinson A.
Validated Reviewer
Review Source

"A Key-value database with high reliability and scability."

What do you like best?

It can get any simpler than a couple commands to get it up and running. It doesn't matter either you need a database for something as simple as a ToDo implementation or something more complicated as a forum, Redis can do that and much more.

What do you dislike?

Being a membased db, it all comes down to physical memory. If you're running in a Low-budget enviroment and a very high traffic towards db data consumption you might encounter a couple issues here and there with Redis, as it can be limited by the hardware or a wrong system configuration.

What business problems are you solving with the product? What benefits have you realized?

As a javascript developer i use a bunch of NoSQL databases. Redis has come handy when i have to deal with low traffic and low sized databases. Personal websites, blogs, maybe some LAN tournament rankings can be done using this as a database engine.

Redis review by Consultant in Veterinary
Consultant in Veterinary
Validated Reviewer
Review Source

"Great in-memory storage and persistance"

What do you like best?

What's best to appreciate about Redis is how quickly it's growing since it's first appearance and how useful and fast it is for many parts of a software implementation.

It always seemed to me like a storage option for caching or indexing, but it is way more than that. Some features are definitely to be highlighted like:

* Pub/Sub message system.

* Redis Cluster

* Expires

* Lua scripting

* Blazing fast

Are some of the things I noticed that make a difference when looking for this kind of memory storage.

What do you dislike?

I did not find any problem yet will update the review one I have more information

What business problems are you solving with the product? What benefits have you realized?

Decoupled architecture, Pub sub

Redis review by L. Preston S.
L. Preston S.
Validated Reviewer
Verified Current User
Review Source

"Redis is easy, and its potential knows no limit."

What do you like best?

I mostly like how there is such a big community around redis. I use redis with ruby on rails, and I just keep coming up with uses for it! All the apis they provide and then are available via the redis-rb gem make accessing redis dead simple.

What do you dislike?

Redis has never disappointed me, so I don't have anything I don't like about it.

Recommendations to others considering the product

Redis is a dream when you use the redis-rb gem.

What business problems are you solving with the product? What benefits have you realized?

I'm using it for helping with background task running, for confirming emails, for inviting collaborators, and soon for aiding in deploying of my ember front-end.

Redis review by Abdel K.
Abdel K.
Validated Reviewer
Review Source

"Best in memory solution "

What do you like best?

The best feature I like is the ability to do chain slave replication, to alleviate some of the load on the master. Its also very easy to integrate, regardless of the language you choose.

Another very useful feature of Redis is the ability to do set theory computation easily.

What do you dislike?

There is very little to dislike about Redis. The only thing I can complain about is clustering. Its not very easy to setup a cluster but once you get the hang of it, then it becomes a bit easier.

Recommendations to others considering the product

If your considering a caching solution or some number crunching. Redis is perfect.

What business problems are you solving with the product? What benefits have you realized?

We used Redis to do a all of our set theory computation on data we retrieve from social media. With the built in sets, it was a perfect off the self solution.

Redis review by Changlang K.
Changlang K.
Validated Reviewer
Verified Current User
Review Source

"Redis performces excellently"

What do you like best?

Redis is very friendly to new user, even who even know any data structure can use redis easily. And it's quite fast search a value by given key.

What do you dislike?

Missing statistic functions, like sum, count, max, min in mysql. Sometimes i just want to find out how many keys starting with "mp", i have to use "keys mp*" to load all such keys.

What business problems are you solving with the product? What benefits have you realized?

I use redis for process synchronization, such as locking resources to guarantee consistency. And I have a query system using redis for key-value storage where key is retrieved from sentence.

Redis review by Brad K.
Brad K.
Validated Reviewer
Review Source

"Redis for realtime xml flight data management"

What do you like best?

Fast, easy to set up. Did I say fast ? Redis met all of our expectations for managing constant stream of flight data in XML, with very frequent object updates. Using Java, the Jedis library was easy to use and intuitive once I had my head around the Redis command language. Redis has great client support across multiple languages as well. The expiration feature is also crucial for our application. Most other databases you would need to create a background task to look for items that need to be garbage collected. With Redis you can set an expiration and it will remove it for you, unless you touch the item again and reset the expiration.

What do you dislike?

No way to really build a "table" (list of hashes) without Lua scripting. This is a capability where you really have to build your own lists, then have those list elements point to a separate hash object to achieve this.

What business problems are you solving with the product? What benefits have you realized?

Realtime flight data storage in XML. Use of sets for access control lists.

Redis review by Bryan H.
Bryan H.
Validated Reviewer
Review Source

"Solid product with some limitations "

What do you like best?

Small feature set, predictable performance, auto-expiry of data, very fast, very simple text based protocol, simple administration, easy to understand where your data is and what's happening to it.

What do you dislike?

I can't say I was enormously pleased when they introduced Lua scripting. The main selling point of the data store was it's simplicity and predictable performance. It would have been preferable that a couple more commands be implemented in C rather than bring stored procedures into the mix. That choice was probably based more on product development than customer need, and again the main attraction was the premise of simplicity. In fairness, it's been a couple of years since I last used it in production so perhaps it's worked out really well since then.

Recommendations to others considering the product

Why not give it a try? It's simple enough that you can get it running in 10 minutes. The basic commands don't take a lot longer to master, and there's some advanced stuff you can do later. I would consider it ideal for transient data storage.

What business problems are you solving with the product? What benefits have you realized?

I've used it for auto-expiring caches, it's great for that particular use-case. Can also be used as a convenient buffer for batch processes. I wouldn't put anything into Redis that I couldn't afford to lose, I guess it's more like memcached in that respect.

Redis review by Fernando H.
Fernando H.
Validated Reviewer
Verified Current User
Review Source

"Fast access to data"

What do you like best?

Simple and fast access to key/value data, as well as score and rank system.

What do you dislike?

Not so easy to find/list existing keys. On the order hand, if you need list keys, probably you are doing something wrong.

What business problems are you solving with the product? What benefits have you realized?

Cache, temporarily data, message queue, non persistent data, in memory database.

Redis review by Henry K.
Henry K.
Validated Reviewer
Review Source

"Excellent tool"

What do you like best?

Redis is a very reliable in-memory database with persistency. I've had great experiences using it both as a message broker and as a cache database. It is certainly a tool that I'll pick whenever I need cache or memory consistency between multiple microservices or atomic message passing through publish/subscribe.

What do you dislike?

I don't recall having bad times with redis.

Recommendations to others considering the product

It is a very useful tool and I'd always recommend it in first place instead of other options in the market.

What business problems are you solving with the product? What benefits have you realized?

I've used redis as a cache service, which has been excellent and also as a middleware between microservices, passing messages through publish/subscribe with namespace and wildcards.

Redis review by Milad T.
Milad T.
Validated Reviewer
Review Source

"Redis - Fast and efficient In-Memory data structure server"

What do you like best?

Redis is a great piece of software. Stability and safety is among my top concerns when it comes to choosing suitable software ro fit my needs. It has a great community and its used in enterprise.

What do you dislike?

None. I had no problems so far with Redis.

Recommendations to others considering the product

Add your own data structures into Redis.

What business problems are you solving with the product? What benefits have you realized?

I use Redis to simulate message passing and mdispatching between many nodes among a cluster of machines. Because of its responsiveness and great networking capabilities ( it uses epoll on linux ), it can easily manage thousands of requests per second for exchanging data between nodes. It is highly optimized and efficient for this purpose.

Redis review by Tong (Tony) J.
Tong (Tony) J.
Validated Reviewer
Review Source

"Practical tool for caching"

What do you like best?

Fast performance, easy to use. Has support for basic data types, and more advanced ones such as HyperLogLog for solving count-distinct problems.

What do you dislike?

There is no native wildcard support for deletion operations in Redis command line client.

Recommendations to others considering the product

Setup multiple DBs for different general use with different default TTLs.

What business problems are you solving with the product? What benefits have you realized?

Caching for web service. Active session tracking/counting.

Redis review by Prashanth G S.
Prashanth G S.
Validated Reviewer
Review Source

"Used as a cache between DB and application"

What do you like best?

The data structure in Redis are very helpful. The set operations helped in efficiently organizing the data and less operation needed from our end. We maintained all the Database relationship in Redis for faster access.

What do you dislike?

No operation on the keys can be performed. Like sorting list based on key. There is a work around, which didn't perfectly fit well

Recommendations to others considering the product

Easily to use. Can build a prototype in a week(depends on what you want to do). Highly recommend to use

What business problems are you solving with the product? What benefits have you realized?

The main problem was to make the client as light as possible. Fetching data from DB was really slow for our flask application. So we thought Redis was the way to go. Where all the data are cached with drastically reduced the REST response time.

Redis review by User
User
Validated Reviewer
Review Source

"I've used Redis along side MySQL for dynamic web page development."

What do you like best?

I have used Redis as a back end for dynamic applications for a web browser. Redis is great for use with user session data and values that need to be reached and updated quickly and often. It wouldn't be optimal for long term storage.

What do you dislike?

One positive and negative of Redis is the fact that it keeps its data in memory. This makes it much faster for updating and calculating numbers and data but if the database crashes the data can't be restored.

Recommendations to others considering the product

Great choice and definitely worth trying!

What business problems are you solving with the product? What benefits have you realized?

I recently have been using Redis as part of a configuration for an WebGL game vaguely similar to agar.io. Redis has allowed our application to quickly update values that are constantly changing in the 3D environment. This has made our application much more scalable as well as easy to maintain.

Redis review by Internal Consultant in Management Consulting
Internal Consultant in Management Consulting
Validated Reviewer
Verified Current User
Review Source

"Redis - replacing AppFabric"

What do you like best?

Fundamentally simple enough concepts.

Lots of resources, can learn fairly the whats and hows.

What do you dislike?

no automated persistence of what gets changed in the cache

Recommendations to others considering the product

Usual PoC approach. Don't assume that, since it worked fine for others, it'll work for you too out of the box, even if use cases are very similar. One should learn it hands-on - no different from other critical infrastructure components.

What business problems are you solving with the product? What benefits have you realized?

Acceleration of reads for frequently-used complex data

Redis review by Chong G.
Chong G.
Validated Reviewer
Verified Current User
Review Source

"Redis in nodejs"

What do you like best?

easy to use, good for handling user sessions in server side

What do you dislike?

now i haven't found something that i don't like or feel terrible

Recommendations to others considering the product

if you want to handle user sessions in a much easier way with node.js, then choose redis :)

What business problems are you solving with the product? What benefits have you realized?

user sessions handling, much more easier than using a relational database to do it

Redis review by User in Internet
User in Internet
Validated Reviewer
Review Source

"middle level of using experience with Redis in application backend"

What do you like best?

1, great performance metric in the perspective of both capacity and latency

2, reliable in production environment

3, simplicity of utilization with good documentation, community, ecosystem and comprehensive data structure

What do you dislike?

getting bigger and bigger, like clustering in the new version, i personally believe simplification is almost always the key of successful.

redis is probably the best in cache. It looks like redis wants to really scale out with cluster, integration or following the way of Cassandra with tunable ability between C and A, leave this choice to the application/users.

Recommendations to others considering the product

Good to use for most of business if you use it in a reasonable way. But do not abuse it, it cannot solve all the problems unless you design the system very carefully in the very beginning, especially in large scale critical business problem, which is always hard to solve anyway.

What business problems are you solving with the product? What benefits have you realized?

Documentation indexing and serving.

In multiple region case. it is getting to expensive to use.

Redis review by User in Higher Education
User in Higher Education
Validated Reviewer
Review Source

"Redis, an underrated database that is really good"

What do you like best?

It's an in-memory database and is very fast. Its operation is not very complex and it has APIs for multiple languages. Therefore people need not be language-bound for better performance. It also has counters and lists to which data can be added atomically.

What do you dislike?

The way Redis operates is by having all the data being handled, in-memory. It cannot persist partial data in memory and the rest on disk. While disk has been getting cheaper, memory is still quite expensive. So that makes using Redis quite expensive.

Recommendations to others considering the product

If you want a key-value store for data which is not huge, Redis can be very helpful, because it stores all the data it's operating on in memory. However, for Big Data, I would recommend HBase or Cassandra because they have been built to handle such a scale.

What business problems are you solving with the product? What benefits have you realized?

We needed to store information such that it can read, modified and stored again. While the MySQL blob data type can be used for a similar purpose, Redis is a lot faster for such a use case.

Redis review by Aryan B.
Aryan B.
Validated Reviewer
Verified Current User
Review Source

"Easy to use"

What do you like best?

Easy to use! You don't have to be geek for using redis. Easy setup, easy configuration and easy query.

What do you dislike?

There is not free default monitor for redis.

Recommendations to others considering the product

Configure max memory usage, if you not there is a risk of use all of your memory.

What business problems are you solving with the product? What benefits have you realized?

Realtime IP banner.

Redis review by Administrator in Hospital & Health Care
Administrator in Hospital & Health Care
Validated Reviewer
Review Source

"DB Action needs redis"

What do you like best?

For rapidly changing data with a foreseeable database size (should fit mostly in memory).

Disk-backed in-memory database,

Master-slave replication, automatic failover

Simple values or data structures by keys

What do you dislike?

Data set size limited to computer RAM (but can span multiple machines' RAM with clustering)

Complex operations like ZREVRANGEBYSCORE.

Bit operations (for example to implement bloom filters)

Recommendations to others considering the product

Give redis a try

What business problems are you solving with the product? What benefits have you realized?

To store real-time stock prices. Real-time analytics. Leaderboards. Real-time communication. And wherever you used memcached before.

Has sets (also union/diff/inter)

Has lists (also a queue; blocking pop)

Has hashes (objects of multiple fields)

Sorted sets (high score table, good for range queries)

Lua scripting capabilities (!)

Has transactions (!)

Values can be set to expire (as in a cache)

Pub/Sub lets one implement messaging

Redis review by José M V.
José M V.
Validated Reviewer
Review Source

"Asynchronous data management done well!"

What do you like best?

Easy setup using it with Ruby, when you need some sort of cache-like storage, Redis is the one you might be looking for.

What do you dislike?

Redis is like a memory datastore, so you won't be able to store anything above your server's memory.

Recommendations to others considering the product

If you're looking for some data storage or easy access db to keep simple logs, maybe using it for a live chat or rankings, Redis can do the job in an awesome way.

What business problems are you solving with the product? What benefits have you realized?

Really fast deployment, easy to setup

Redis review by Gautam K.
Gautam K.
Validated Reviewer
Verified Current User
Review Source

"Quite Brilliant"

What do you like best?

I love the simple setup and the sane defaults offered by redis.

What do you dislike?

I wish there were pre-built binaries available for popular Linux distros instead of me downloading and compiling from source.

Recommendations to others considering the product

Go for it. Redis is something you won't regret.

What business problems are you solving with the product? What benefits have you realized?

Session Caching.

Redis review by Felipe L.
Felipe L.
Validated Reviewer
Verified Current User
Review Source

"Excelente to use with cache database"

What do you like best?

Simple to use, you can use together AWS Elastic Cache, pretty easy to use.

What do you dislike?

Doesn't has good tool to management data, but exists. I usually use implementation in nodejs called "Redis Commander".

Recommendations to others considering the product

Sure, is better than memcached, so much fast and new.

What business problems are you solving with the product? What benefits have you realized?

I use in my main app, in-memory cache (AWS elastic cache - Redis), it is so fast, I like so much.

Redis review by Dimitar M.
Dimitar M.
Validated Reviewer
Review Source

"Redis - essential for high scalability."

What do you like best?

I absolutely love the speed of Redis. I like Redis's high level operations and features. Its easy to setup and deploy.

What do you dislike?

The clusterization could be better. It's kinda naive with no master/master replication and monitoring. It's important for me. I hope it gets better.

Recommendations to others considering the product

Always use latest version and stick with proven concepts.

What business problems are you solving with the product? What benefits have you realized?

The problem that we solved with Redis was synchronising websocket communication between several nodes using pub/sub. It's easy to setup and works great.

Redis review by Executive Sponsor in Internet
Executive Sponsor in Internet
Validated Reviewer
Verified Current User
Review Source

"Great experience with Redis"

What do you like best?

Super fast response times (main purpose of redis)

What do you dislike?

Data is stored in memory (needed for the quick retrieval of the data). This is generally not an issue, however very large datasets (> 250 GB) can't be fully stored in the memory and redis might not the best option for very large sets.

What business problems are you solving with the product? What benefits have you realized?

Fast retrieval of product recommendations. Normal SQL requests take too long with larger datasets. Redis requires that the data is organized differently, but the extra work upfront pays off with every data request.

Redis review by User
User
Validated Reviewer
Review Source

"A good nosql solution"

What do you like best?

Redis is a good solution if you are searching for something different of SQL structure.

It can be used in different ways depending on the needs, we have used mainly as a cache exploiting its speed of interrogation by key-value.

What do you dislike?

As for the use that I did, just some initial difficulties in being able to interpret, understand and use correctly the query language by Key

What business problems are you solving with the product? What benefits have you realized?

Some queries to the relational database have been optimized thanks to the aid of the memory in the cache, thus avoiding to make an excessive number of calls to the DB and thus lowering the work load on SQL servers.

Redis review by Anson A.
Anson A.
Validated Reviewer
Review Source

"redis"

What do you like best?

ease of use, and ease of setup. Very fast for a KV store for reads and writes

What do you dislike?

only one master...not a masterless type cluster, which would be great

What business problems are you solving with the product? What benefits have you realized?

needed a fast kv store for quick lookups. Using it mostly for cacheing of datasets for reports.

Redis review by Internal Consultant in Telecommunications
Internal Consultant in Telecommunications
Validated Reviewer
Verified Current User
Review Source

"Redis is easy to use"

What do you like best?

It is simple cache-storage software and easy to use. I have no problems incorporating it into any of my projects.

What do you dislike?

That it isn't easy to setup and use on Windows (compared to a *nix) environment.

What business problems are you solving with the product? What benefits have you realized?

I am using Redis to store cache information - such as commonly referenced language values, user profile information, and any other data that needs to be access very quickly.

Redis review by Caio C.
Caio C.
Validated Reviewer
Review Source

"Redis is fast and simple"

What do you like best?

I like how easy is to setup and maintain. Also that is very fast.

What do you dislike?

Some commands names are difficult to understand and its hard to know what they do in an intuitive way.

Recommendations to others considering the product

If you need a fast and simple to handle database to use its the right pick.

What business problems are you solving with the product? What benefits have you realized?

I need to develop an application that required a nosql and real time performance.

Redis review by Dan B.
Dan B.
Validated Reviewer
Review Source

"Redis"

What do you like best?

Lots of different languages bindings, so you're able to use redis in every language. The install was very quick and it was easy jump into.

What do you dislike?

I didn't find anything I disliked, I only scratched the surface and didn't touch any of the more controversial features.

What business problems are you solving with the product? What benefits have you realized?

I needed a simple key-value store and redis was able to fulfill everything I wanted.

Redis review by Levi D.
Levi D.
Validated Reviewer
Review Source

"Redis simple review"

What do you like best?

Speed of the database. I also really like the documentation on the redis website, it made it easy to learn.

What do you dislike?

The learning curve, it was very different than other traditional databases. You could also put this in the like column, as I liked the challenge.

Recommendations to others considering the product

Get to know the redis.io website, it's your best friend

What business problems are you solving with the product? What benefits have you realized?

Leaderboards were the main use for redis in this instance, and it was amazingly fast compared to other traditional databases.

Redis review by Industry Analyst / Tech Writer in Internet
Industry Analyst / Tech Writer in Internet
Validated Reviewer
Review Source

"Amazed by the response time and works great for applications that need high read and write access."

What do you like best?

As mentioned in the title, Redis is fast and accurate. This makes certain tasks easier since most of the times, we don't have to rely on data stored on disk.

What do you dislike?

To be honest, I didn't use Redis for considerable amount of time to nit pick anything. All in all, I liked it as it was.

Recommendations to others considering the product

Improvements on documentation would certainly help.

What business problems are you solving with the product? What benefits have you realized?

So we wanted to store the customer profile information and we didn't wanted to use relational databases since it becomes too complicated to use. In essence to Redis, it is very easy to change the structure and I don't have to write big queries to fetch customer related information.

Redis review by Roman K.
Roman K.
Validated Reviewer
Review Source

"Redis is the "must known" tool for backend developers."

What do you like best?

- Redis is open source

- Speed of work

- Publish/Subscribe messaging paradigm support

What do you dislike?

The Redis does not officially support Windows. I believe that redis should be easily installed on all popular OS.

What business problems are you solving with the product? What benefits have you realized?

I'm use redis in my web-based projects as a session and cache system. The main benefits is speed and easy development.

Redis review by User in Internet
User in Internet
Validated Reviewer
Verified Current User
Review Source

"Awesome"

What do you like best?

Free

Opensource

Simple to use

Very performant (it's written in C)

Supports lots of data structures and commands (for a simple KV store)

Great client support

What do you dislike?

Cluster support took to much time to be released

Better/more stable cluster support (better admin tools for creating/managing a cluster)

What business problems are you solving with the product? What benefits have you realized?

Mostly data storage.

Redis review by User in Computer Software
User in Computer Software
Validated Reviewer
Review Source

"Redis: the backbone of multi-process communication"

What do you like best?

Whether you need a producer-consumer implementation that scales to thousands of machines or an application monitoring and servicing protocol, Redis is one of the best tools out there.

What do you dislike?

It took the community a long time to deliver Redis Cluster and, as of this writing, it is a brand new implementation that has yet to be battle hardened.

What business problems are you solving with the product? What benefits have you realized?

Redis is great for solving the business problem of enabling web-scale and easy maintainability while using the most popular web-development languages and platforms. The former is required to deliver value to customers while the latter is required to attract top talent.

Redis review by Никита .
Никита .
Validated Reviewer
Review Source

"Advanced memcached"

What do you like best?

Easy to setup, great docs, simple protocol. Last commit 12 hours ago :-)

What do you dislike?

Did not see any real word clustering cases in web, caveats etc.

What business problems are you solving with the product? What benefits have you realized?

Use it for caching instead of memcached and for storing "not so important" data. For example 404 pages logging with counters.

Redis review by 志龙 .
志龙 .
Validated Reviewer
Review Source

"Use to build the cache bachground is very quickly and conveniently"

What do you like best?

Favorite redis running speed and operating convenience, I can quickly build a background application. Especially with redis caching function when, redis can satisfy demand.

What do you dislike?

redis data persistence and is not easy, redis need to provide a more convenient way to secure data persistence.

What business problems are you solving with the product? What benefits have you realized?

caching

Redis review by Geremy C.
Geremy C.
Validated Reviewer
Review Source

"Easy to use key / value store"

What do you like best?

Very easy to install, setup, and get to hello world with.

What do you dislike?

Like many things, the basic setup and use case is easy, but to do HA, scaling, it takes a lot of knowledge of the system.

What business problems are you solving with the product? What benefits have you realized?

I have used it as a high-speed cache for Ruby for web applications, caching ERBs, as well as full views.

Redis review by Administrator in Computer Software
Administrator in Computer Software
Validated Reviewer
Verified Current User
Review Source

"Simplicity is Beauty and Beauty is simplicity."

What do you like best?

The performance , robustness , easy to learn and ease to use in production environments .

What do you dislike?

scripting language , i prefer that use javascript for scripting in redis .

Recommendations to others considering the product

support javascript as scripting language and connecting and integrating to another databases as an optional module .

What business problems are you solving with the product? What benefits have you realized?

we are using redis in data caching and socket.io related using .

Redis review by User in Internet
User in Internet
Validated Reviewer
Review Source

"Blazing fast, scales well"

What do you like best?

* Simple to use API

* Wide range of command (list, set, sorted set, hash etc)

* Blazing fast

* Very scalable

What do you dislike?

Clustering was not straight forward, but redis 3.0 solves this

Recommendations to others considering the product

Get a lot of ram.

What business problems are you solving with the product? What benefits have you realized?

1. While redis as a cache like memcache, it offers a lot of advantages with its advanced data structures, which make appending data easier. Also getting partial data out of the cache is possible (using range).

2. Using redis as a database has enabled very high write through puts.

Redis review by Administrator in Internet
Administrator in Internet
Validated Reviewer
Review Source

"Scalability."

What do you like best?

We work with Redis in most of our projects and this tool is awesome. It helps us to scale our services and apps easily. It is simple and effective!

What do you dislike?

Sometimes your simple API is not enough. I think there are some things to improve there.

What business problems are you solving with the product? What benefits have you realized?

We are one of the greatest media company in Brazil and we need to provide scalable systems. Redis turn our architecture simpler.

Redis review by User
User
Validated Reviewer
Review Source

"Redis provides an easy to use, scalable key-value store."

What do you like best?

I like the ease of use that redis provides. Not only that, but it isn't limited by language so that it can be used in ruby, python, c, or any number of other languages.

What do you dislike?

It does take a lot of space to store the empty string, so there are some parts to be wary of.

What business problems are you solving with the product? What benefits have you realized?

Scaling. Redis makes scaling easy

Redis review by User in Information Technology and Services
User in Information Technology and Services
Validated Reviewer
Review Source

"The essential tool for any distributed system"

What do you like best?

The ability to easily handle things like sessions in a distributed environment without having to spend much time.

What do you dislike?

The limitations on some features that come when running a cluster.

What business problems are you solving with the product? What benefits have you realized?

Moving from a centralized server to micro services and a distributed high availability setup.

Redis review by User in Internet
User in Internet
Validated Reviewer
Review Source

"Redis for Sidekiq and caching"

What do you like best?

Redis is extremely fast to set up, easy to use, and acts as a great light-weight key-value store.

What do you dislike?

It's extremely annoying that Redis does not support SSL by default.

Recommendations to others considering the product

You'll need to setup stunnel for it.

What business problems are you solving with the product? What benefits have you realized?

We primarily use Redis for caching and as a queue for background jobs.

Redis review by Administrator in Gambling & Casinos
Administrator in Gambling & Casinos
Validated Reviewer
Review Source

"Website cache"

What do you like best?

easy to use, fast and reliable. perfect for high availability

What do you dislike?

some problems during installation, nothing important but it should be easier. ok for data manipulation but i think not so fast for that

What business problems are you solving with the product? What benefits have you realized?

we've boosted cache performance in a business website using redis

Redis review by User
User
Validated Reviewer
Review Source

"Developer"

What do you like best?

Good to get data in real time, easy to use, easy to scale.

What do you dislike?

Sometimes the syntax is a bit limitating.

Recommendations to others considering the product

Give it a go, it's very easy to get started.

What business problems are you solving with the product? What benefits have you realized?

Getting users data in real time. I was impressed by the low latency.

Redis review by Administrator in Internet
Administrator in Internet
Validated Reviewer
Review Source

"Using as a project database. Good enough"

What do you like best?

open source, good integration, fast and convenient

What do you dislike?

not too much, maybe not enough tutorials when I try to look more deeper in it,

What business problems are you solving with the product? What benefits have you realized?

really easy to start using, pretty straight forward and easy to use,

I used Redis to build a course project relate to auto-web-crowler

Redis review by Administrator in Computer Software
Administrator in Computer Software
Validated Reviewer
Review Source

"works great depending on use case"

What do you like best?

simple and easy to use. support is great and documentation is good

What do you dislike?

small feature set. they need to expand the tools and feature set.

What business problems are you solving with the product? What benefits have you realized?

semi persistent data.

Redis review by Administrator in Information Technology and Services
Administrator in Information Technology and Services
Validated Reviewer
Review Source

"How to have a fast key value datastore for your app"

What do you like best?

Speed, easy of config and management of the caches

What do you dislike?

Not easy in clustering option and some options needed more research

What business problems are you solving with the product? What benefits have you realized?

Gambling company. Caching

Kate from G2 Crowd

Learning about Redis?

I can help.
* We monitor all Redis reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. Validated reviews require the user to submit a screenshot of the product containing their user ID, in order to verify a user is an actual user of the product.