The easiest route - we'll conduct a 15 minute phone interview and write up the review for you.
Use our online form to submit your review. It's quick and you can post anonymously.
We use it primarily for real-time applications. In our web application, we added a feature where hundreds of people could play a quiz in real time.
Instead of using traditional databases like SQL, we implemented Redis to make everything happen in real time – all those quick calculations, data hashing for easy retrieval, and so on.
It was a live quiz feature, so Redis helped a lot. I also use Redis for caching and similar general use cases.
It improved the performance. For example, data structures like hashmaps in Redis make it a very fast database – much faster than traditional SQL databases. It can perform at significantly higher speeds. Latencies are very low. Our primary focus wasn't on saving money but on improving performance for that specific feature.
So, performance has been the key improvement. Every calculation happened in real time. It improved the performance 10X.
In our company, we have limited resources, so we can't manage the database ourselves. We use services from Azure for that. So, Redis integrates well with those services.
We use Azure Cache for Redis.
It performs much better than traditional databases. Our calculations happen in real-time, which was crucial for that quiz feature.
The price could be better.
I have been using it for more than two years.
It has been a reliable product for us.
It's been working very well for us. Since our scale isn't huge, it's able to handle our needs without issues.
I've also worked with PostgreSQL, Cassandra, MySQL, and Elasticsearch.
It's tough to find a direct competitor because Redis, Cassandra, PostgreSQL, and Elasticsearch all serve different purposes. Cassandra excels when you structure tables according to your requirements upfront. It offers fast reads. However, the Cassandra Query Language (CQL) isn't as flexible as SQL – there are no joins, for example. It is a very restricted query language. So, we need to carefully design your database tables with future data needs in mind.
Redis is better tested and is used by large companies. I haven't found a direct alternative to what Redis offers. Plus, there are a lot of support and learning resources available, which help you use Redis efficiently.
It's actually quite expensive compared to SQL since Redis uses a system's main RAM, which is costly. And memory can be limited.
We opt for a dedicated server.
Overall, I would rate the solution an eight out of ten. It's been very stable so far and performs well within our system.
I would recommend it, but I would also highlight the cost factor as something to consider.
I have been using a specific infrastructure. We use it primarily for customer service.
It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology.
The only thing is the lack of a GUI application. There was a time when we needed to resolve an issue in production. If we had a GUI, it would have been easier. But no one provided a GUI, or maybe we didn't request it. I'm not sure. We just make use of it.
My experience with this product has been very good.
It's been very stable. I would rate the stability a ten out of ten.
We saw an ROI. It made the processing of our transactions faster. So there are some details we get, like customer contract details, customer details, customer ID, there are so many details for that. So we get it from Redis, which makes it faster.
I would rate it an eight out of ten.
I would recommend to explore this product as it's gonna make the work easy.
