Redis has been a strong addition to our stack at CargoX, mainly used for caching and session management alongside our Express.js backend. The interface and tooling around it are simple and don't require much overhead to manage day-to-day. It integrates cleanly with our existing Node.js and Express setup, requiring minimal configuration to get caching layers working effectively. Performance has been excellent, with noticeably faster response times for frequently accessed data and reduced load on our primary database. Being open-source with a strong free tier makes the ROI very favorable, especially since we haven't needed enterprise features to get significant value. Documentation and community resources are extensive, so onboarding new developers into using Redis within our stack has been quick without needing formal support. There's no built-in AI or intelligence layer, but for a caching and data store tool, that hasn't been a limitation for our use case. Review collected by and hosted on G2.com.

The command-line interface, while powerful, isn't the most beginner-friendly, so newer team members needed some ramp-up time before getting comfortable with Redis-specific commands and data structures. Integrating persistence configurations properly took some trial and error to avoid data loss risks in edge cases, since the default settings prioritize speed over durability. Performance is excellent for in-memory operations, but memory usage can grow quickly if key expiration and eviction policies aren't managed carefully, which requires ongoing attention as data volume scales. Pricing for Redis Enterprise or managed cloud offerings can get expensive if you outgrow the free, self-hosted setup, and support for the open-source version relies entirely on community resources rather than dedicated channels. There's also no AI-driven optimization for cache eviction or memory management, so tuning performance still depends on manual configuration and experience rather than any intelligent automation. Review collected by and hosted on G2.com.

What I like most about Redis is its exceptional performance and simplicity. It's incredibly fast for caching, session storage, queues, and temporary data management. Review collected by and hosted on G2.com.

Memory management and debugging issues are hard to manage. Review collected by and hosted on G2.com.

I really like the Active-Active geo-distribution feature in Redis Software. It mirrors writes from our Haryana data center to our Mumbai replica in under 50ms and automatically handles failovers. This setup handled double the normal traffic during Diwali, managing over 2 million session tokens without a hiccup. Redis Software's Redis on Flash also significantly cut our RAM usage by 60%, which is a huge benefit for our large datasets. The initial setup was surprisingly smooth too, with the installer getting a 3-node cluster running on our Kubernetes setup in less than an hour using a guided UI, greatly reducing the manual configuration workload. This lets our team focus more on the application layer rather than infrastructure headaches. Review collected by and hosted on G2.com.

I find the steep licensing (~₹50K/node/year) challenging for SMBs after the trial compared to fully open-source stacks. The UI dashboard lags on clusters with more than 100 nodes—kubectl metrics outperform Redis Insight for real-time CI/CD monitoring, which forces us to use hybrid tooling during deployments. Review collected by and hosted on G2.com.

Its one of the best software out there for the low latency key store. It comes handy for managing and maintaining session information in the security layer of a distributed web application. Review collected by and hosted on G2.com.

The redis sentinal based distributed deployment in container runtime is bit difficult to configure. Review collected by and hosted on G2.com.

Easy to implement for the projects I usually work on, like Python and Data projects and also the projects in which I have to implement Large Language Models. Review collected by and hosted on G2.com.

Sometimes for a huge amount of data, it takes a lot of time to do embedding which is why the semantic search and the overall time of the process becomes greater Review collected by and hosted on G2.com.

Just amazing product. love to use as main cache provider Review collected by and hosted on G2.com.

honestly, there is nothing much to say. no dislike. Review collected by and hosted on G2.com.

I can use as queue for pub-sub architecture and fast performance Review collected by and hosted on G2.com.

Low data structure support and Backup for large scale application to reduce downtime. Review collected by and hosted on G2.com.

Redis uses the power of a general database as well as in-memory storage, which makes Redis easy to use from a developer's POV and powerful as in-memory storage. It supports all programming languages similar to other general databases. That's why easy to integrate and implement as start using Redis to make the software faster. Review collected by and hosted on G2.com.

Redis doesn't support join or rich query language. Review collected by and hosted on G2.com.

Redis is very very easy to use. We use it in our software to get frequently used data from cache instead of db which saves a lot of time in computation. Plus its pub sub system is also helpful in some areas of our software. Review collected by and hosted on G2.com.

No UI to see all its keys and values. One has to be dependent on its command line interface. Review collected by and hosted on G2.com.

It is very simple to set up and use once you learn the basics. The data types are very basic, but extremely performant. Redis is used every day as a main part of the tech stack. Review collected by and hosted on G2.com.

The lack of out-of-the-box support for JSON structures. Review collected by and hosted on G2.com.