Item: Redis™*
Rating: 7
Author: Verified User

Use Cases and Deployment Scope

We use it to manage & control user sessions in a Tomcat based web application programmed with Java. It's used in both production and testing & development environments in this certain application's server backend, but only the software development department actually understands & manages it. It solves the case to keep users logged in to the application and also invalidates the sessions when requested or automatically if they expire.

Pros and Cons

Has been working well for storing user sessions.
No need for maintenance operations. Once it's set up has been working flawlessly.
Many configuration options, little programming required.

The actual database structure is difficult to understand.
Only command line application available for free. Difficult to use.
Seems to have some encoding issues when inspecting data directly with CLI app.

Return on Investment

Free to use and easy to integrate with other technologies. Doesn't take much development days.
Has not required any support from developers after initial implementation.

Key Insights

Do you think Redis™* delivers good value for the price?

Yes

Are you happy with Redis™*'s feature set?

Yes

Did Redis™* live up to sales and marketing promises?

Yes

Did implementation of Redis™* go as expected?

Yes

Would you buy Redis™* again?

Yes

Other Software Used

Apache Tomcat, MySQL, MongoDB

Usability

It is quite simple to set up for the purpose of managing user sessions in the backend. It can be easily integrated with other products or technologies, such as Spring in Java. If you need to actually display the data stored in Redis in your application this is a bit difficult to understand initially but is possible.

Support Rating

I have not needed to contact support team and have managed to implement use cases with freely available information online.

Likelihood to Recommend

It is well suited when a web application needs to store any kind of user sessions. It works both for storing logged in user sessions but also for non authenticated users. User sessions are temporary; however, for storing permanent data that needs to be retained across sessions it is not appropriate because Redis is an in-memory database.

Set up & forget

Overall Satisfaction with Redis