No more typing reviews! Try our Samantha, our new voice AI agent.

OpenLegacy vs Redis comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

OpenLegacy
Ranking in AI Software Development
62nd
Average Rating
7.6
Reviews Sentiment
6.2
Number of Reviews
5
Ranking in other categories
API Management (32nd)
Redis
Ranking in AI Software Development
8th
Average Rating
8.8
Reviews Sentiment
6.6
Number of Reviews
26
Ranking in other categories
NoSQL Databases (3rd), Managed NoSQL Databases (5th), In-Memory Data Store Services (1st), Vector Databases (5th)
 

Mindshare comparison

As of October 2026, in the AI Software Development category, the mindshare of OpenLegacy is 0.4%, up from 0.1% compared to the previous year. The mindshare of Redis is 0.5%, up from 0.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
AI Software Development Mindshare Distribution
ProductMindshare (%)
Redis0.5%
OpenLegacy0.4%
Other99.1%
AI Software Development
 

Featured Reviews

reviewer1042905 - PeerSpot reviewer
VP, Chief Enterprise Integration Architect at a financial services firm with 10,001+ employees
The biggest advantage is how simple the technology was.
I'd like to see OpenLegacy develop its low-code/no-code (LCNC) solutions. They've expanded somewhat their horizons for integration beyond mainframe CICS, which is their sweet spot. They have some tooling in that area, but it's not as good as it needs to be. OpenLegacy handles the bread-and-butter TP monitoring stuff, but I am working for one of the six banks in the United States still using the Hogan mainframe, which has a slightly proprietary mechanism. But OpenLegacy currently doesn't have a connector for Hogan. So it would help if they could build one. That would appeal to financial institutions that still use Hogan, like US Bank, Wells Fargo, KeyBank, and Vanguard.
RituRaj - PeerSpot reviewer
SDE 2 at Virtusa
Caching has improved response times and reduces database load for high-traffic applications
Redis is very reliable, but it could be improved in areas such as monitoring, debugging, and feasibility into memory use. Better built-in tools for observability would help teams manage it more effectively at scale. Managing memory efficiently and troubleshooting issues can sometimes require additional tooling, so these areas can also be improved.One practical challenge I experienced is managing memory efficiently. Since Redis is in-memory, we need to carefully configure eviction policies and monitor usage. Debugging cache-related issues such as stale data or cache invalidation can sometimes be tricky. Additionally, tuning memory usage and eviction policies needs to be planned very carefully.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The biggest advantage of OpenLegacy was how simple the technology was, and we were able to build out the OpenLegacy parts very quickly, putting together a couple hundred APIs in six months."
"It is possible to connect a service to a mainframe program or back transaction in a matter of minutes or hours at the most."
"Without OpenLegacy, it would take us several months to create the same services."
"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
"Using OpenLegacy, the exposure of services is far easier and quicker. In many cases, exposure of services requires just a few clicks and takes only minutes. In very complex cases, it still only takes half a day. Without OpenLegacy, it would take us several months to create the same services."
"The speed of development of production, especially in specific environments like IBM mainframes, has been valuable."
"OpenLegacy provides a way to go from the outside world to the legacy mainframe, to move the old standard application to a REST API application. New digital services can be created in a few clicks and this can be done easily by COBOL programmers."
"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
"Redis has had a positive impact by improving application performance, reducing database load, and making the system more scalable."
"Redis is good for distributed caching management."
"Since I started using Redis, I feel that the product is saving me some performance tuning time."
"Redis is a simple, powerful, and fast solution."
"Redis has multiple valuable features such as being a free and reliable open-source tool."
"The performance of Redis is very fast."
"The product offers fast access to my database."
"The in-memory data makes it fast."
 

Cons

"I'd like to see OpenLegacy develop its low-code/no-code (LCNC) solutions. They've expanded somewhat their horizons for integration beyond mainframe CICS, which is their sweet spot. They have some tooling in that area, but it's not as good as it needs to be."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
"The pricing of the solution could be more flexible and allow for once-off payment versus annual licensing. This would be more appealing to companies in Latin America."
"Debugging and logging for programmers could be better."
"We would also be more than happy if the product had the option to work in the opposite direction – the ability to consume REST/SOW services in the outer world from the mainframe."
"I would like to see SSL out-of-the-box. OpenLegacy certainly does SSL, but it was not the default for our use case. We are currently working with OpenLegacy to cross the SSL bridge and suspect that most users will want to do the same."
"There is room for AWS to provide more options for server types or a way to configure more or less memory for them."
"There is a lack of documentation on the scalability of the solution."
"The development of clusters could improve. Additionally, it would be helpful if it was integrated with Amazon AWS or Google Cloud."
"Redis could be improved by introducing a GUI to display key-value pair database information, as it is currently a CLI tool with no visual representation."
"For the PubSub feature, we had to create our own tools to monitor the events."
"Redis should have an option to operate without Docker on a local PC."
"Redis presents a single point of failure and lacks fault tolerance."
"The solution's pricing for a local installation is very expensive."
 

Pricing and Cost Advice

"The pricing of the solution could be more flexible and allow for once-off payment versus annual licensing. This would be more appealing to companies in Latin America."
"We saw an ROI. It made the processing of our transactions faster."
"The tool is open-source. There are no additional costs."
"Redis is not an overpriced solution."
"Redis is an open-source solution. There are not any hidden fees."
"Redis is an open-source product."
report
Use our free recommendation engine to learn which AI Software Development solutions are best for your needs.
915,341 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
24%
Comms Service Provider
14%
Financial Services Firm
14%
Manufacturing Company
10%
Financial Services Firm
22%
Computer Software Company
9%
Comms Service Provider
7%
University
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise6
Large Enterprise10
 

Questions from the Community

Ask a question
Earn 20 points
What needs improvement with Redis?
Making management easier, especially for teams operating large Redis clusters, would be helpful. More advanced built-in observability, performance insights, and automated recommendations would help...
What is your primary use case for Redis?
Redis is used primarily as a caching layer to provide a high-performance caching solution that improves application response times and reduces load on backend services and databases. We use it main...
What advice do you have for others considering Redis?
There are a couple of things to consider when using Redis. It is a supporting layer, not a main database. Identifying specific use cases where Redis can provide the most value, such as caching, ses...
 

Comparisons

 

Also Known As

No data available
Redis Enterprise
 

Overview

 

Sample Customers

Many of openLegacy's global customers are among the Global 100 companies. Review case studies in these industries: Agriculture, Airport Authority, Automotive, Auto, Finance, Insurance, Government, Healthcare, Manufacturing, and Retailwww.openlegacy.com/case-studie...
1. Twitter 2. GitHub 3. StackOverflow 4. Pinterest 5. Snapchat 6. Craigslist 7. Digg 8. Weibo 9. Airbnb 10. Uber 11. Slack 12. Trello 13. Shopify 14. Coursera 15. Medium 16. Twitch 17. Foursquare 18. Meetup 19. Kickstarter 20. Docker 21. Heroku 22. Bitbucket 23. Groupon 24. Flipboard 25. SoundCloud 26. BuzzFeed 27. Disqus 28. The New York Times 29. Walmart 30. Nike 31. Sony 32. Philips
Find out what your peers are saying about OpenLegacy vs. Redis and other solutions. Updated: September 2026.
915,341 professionals have used our research since 2012.