Score 9.2 out of 10


What is Redis™*?

Redis is an open source in-memory data structure server and NoSQL database.
Read more

Recent Reviews

Set up & forget

7 out of 10
May 08, 2021
We use it to manage & control user sessions in a Tomcat based web application programmed with Java. It's used in both production and …
Continue reading

Redis Review

9 out of 10
February 03, 2020
Redis has been a vital component in our design, it's usage is mainly for caching API requests, but it also extends to other applications …
Continue reading

Redis is awesome!

9 out of 10
November 23, 2019
We're using Redis in many ways and across different departments in the organization. The most simple use case is to store locks so the …
Continue reading
Read all reviews


Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Popular Features

View all 7 features
  • Performance (69)
  • Scalability (69)
  • Availability (69)
  • Concurrency (68)

Video Reviews

Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Redis™*, and make your voice heard!

Return to navigation


View all pricing



On Premise
per month

Entry-level set up fee?

  • Setup fee optional
For the latest information on pricing, visit


  • Free Trial
  • Free/Freemium Version
  • Premium Consulting / Integration Services
Return to navigation

Product Demos

Why Redis?
Return to navigation


NoSQL Databases

NoSQL databases are designed to be used across large distrusted systems. They are notably much more scalable and much faster and handling very large data loads than traditional relational databases.

9.2Avg 8.7
Return to navigation

Product Details

What is Redis™*?

According to the vendor, Redis is an in-memory multi-model database that supports multiple data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs and geospatial indexes with radius queries. Redis has built-in replication, Lua scripting, LRU eviction, transactions and different levels of on-disk persistence, and provides high availability and automatic partitioning with Redis Cluster.

Redis combines in-memory, schema-less design with optimized data structures and versatile modules that adapt to your data needs. The result is an adept, high performance, multi-purpose database that scales easily like a simple key/value data store but delivers sophisticated functionality with great simplicity, according to the vendor.

Redis also enables data persistence and high availability through replication and backups. Redis Enterprise is built from the ground up to serve as a system of record for any application.

*Redis is a trademark of Redis Ltd. Any rights therein are reserved to Redis Ltd. Any use by TrustRadius is for referential purposes only and does not indicate any sponsorship, endorsement or affiliation between Redis and TrustRadius.

Redis™* Features

NoSQL Databases Features

  • Supported: Performance
  • Supported: Availability
  • Supported: Concurrency
  • Supported: Security
  • Supported: Scalability
  • Supported: Data model flexibility
  • Supported: Deployment model flexibility

Additional Features

  • Supported: Integrated modules
  • Supported: Active-Passive Geo Distribution
  • Supported: Cluster Architecture
  • Supported: Linear Scaling
  • Supported: Durability
  • Supported: Backup and Disaster Recovery
  • Supported: Reliability

Redis™* Screenshots

Screenshot of Screenshot of Screenshot of Screenshot of Screenshot of Screenshot of

Redis™* Video

Why Redis?

Redis™* Integrations

Redis™* Technical Details

Deployment TypesOn-premise, Software as a Service (SaaS), Cloud, or Web-Based
Operating SystemsWindows, Linux, Mac
Mobile ApplicationApple iOS, Android, Windows Phone, Blackberry, Mobile Web
Supported CountriesGlobal
Supported Languages

Frequently Asked Questions

Redis is an open source in-memory data structure server and NoSQL database.

MongoDB, Amazon ElastiCache, and Couchbase are common alternatives for Redis™*.

Reviewers rate Performance highest, with a score of 10.

The most common users of Redis™* are from Mid-sized Companies (51-1,000 employees).
Return to navigation


View all alternatives
Return to navigation


(1-25 of 61)
Companies can't remove reviews or game the system. Here's why
Score 9 out of 10
Vetted Review
Verified User
We replaced Microsoft SQL because of the cost, maintenance and reliability associated with running a hybrid infrastructure. Also our licenses costs have been reduced since we can re-focus those resources on development.
October 08, 2019

Gets the job done!

Emiliano Perez | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
MySQL - Simply put, we started with MySQL, but it was too slow for our needs once our company started growing out. Clustering MySQL is quite a painful process since any sharding solutions implies losing the MySQL schema or making multiple migrations and risking data loss. Using Redis as a Database fixed our issues.
Leonel Quinteros | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
We replaced some instances of Memcached with Redis.
The main drive for that replacement was the ability of Redis to quickly add data persistence to the in-memory cache functionality. This is super helpful in a microservices environment where all instances can be restarted and redeployed and you don't want to lose data on each deploy. With Memcached, this is impossible to achieve, while with Redis it gets pretty straightforward, without losing performance or availability.
Score 9 out of 10
Vetted Review
Verified User
We used memcached in the past for our cookies and sessions. Redis was the hot new thing, so we tried it out and realized all the hype was reality. Our needs were simple, we couldn't get memcached to span across servers. For web page caching, we used to use a homegrown system that would be stored on disk. Redis was in-memory, so that was obviously a much faster response time.
Return to navigation