Blazing performance, excellent stability, and really nothing to dislike make Redis a must look at solution
Updated October 26, 2023
Blazing performance, excellent stability, and really nothing to dislike make Redis a must look at solution
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with Redis
Redis is being leveraged to address big data, temporal data and session state challenges across the software stack. New opportunities to leverage it are continually being investigated and identified. It addresses data consistency and concurrency issues and provides amazing speed to what could be slower operations if handled without it.
- Cache speed
- Support for high volume of transactions with elegant handling of data sets
- Ease of use - well structured and easy to implement
- Price per shard is a bit high but over all there are no issues worth mentioning
- I've heard some wishing it supported complex queries but this is asking the solution to support operations it wasn't intended for
- Reductions in latency allow operations that would be longer running (multiple seconds) to be performed nearly instantaneously providing for high performance.
- Redis allows for easier application scaling and support for a higher volume of transactions without typical performance curve limitations.
- Savings related to not having to pre-process unstructured data are hard to quantify but very appreciated in the sense of savings on code complexity.
- Product Features
- Product Usability
- Product Reputation
The reputation of Redis was the first element that sparked our interest and it was implemented as a proof of concept (POC) implementation to get an empirical sense of the potential impact and usability/suitability within our application stack. It exceeded expectations with respect to usability and features and proved to be an excellent solution.
Previously (not necessarily as solutions for this application stack) many have used alternatives including Memcached, MongoDB, CouchDB, Cassandra etc., and Redis was tested and compared to these other solutions - if only mentally. Ultimately while they are all good solutions they each target specific use cases (and support different ones better - with potential added complexity for differing feature sets), Redis was the best fit for the types of use cases we are specifically targeting it for.