Redis Reviews

In my current workplace, we use Redis for various purposes, including managing query caches, queues, and as a registry for different system components. These components register themselves when live, enabling efficient usage tracking. 

Previously, at another company, we used Redis to cache machine learning models, facilitating model delivery across platforms without frequent disk retrieval.

In my current workplace, we use Redis for various purposes, including managing query caches, queues, and as a registry for different system components. These components register themselves when live, enabling efficient usage tracking. 

Previously, at another company, we used Redis to cache machine learning models, facilitating model delivery across platforms without frequent disk retrieval.

Redis provides an easy setup and operation process, allowing users to quickly connect and use it without hassle. We primarily use Redis as a caching system due to its multiple data types and PubSub features, offering efficient data handling. Redis's PubSub capabilities benefit our communication by facilitating thread intercommunication. It allows multiple threads to exchange messages efficiently.

Redis presents a single point of failure and lacks fault tolerance. It would be beneficial if high availability features were available in the noncommercial version, similar to those offered by the commercial managed solutions from Redis Labs.

I have been working with Redis for over ten years.

If Redis is set up correctly, it requires no maintenance and can function smoothly for long periods without intervention. Memory calculations should be precise to avoid issues.

With approximately 500 microservices and environments scaling up to 1,000 customers, Redis accommodates a range of scales. Proper memory allocation allows for seamless operation.

We have not utilized customer support for Redis.

In comparison to other caching solutions like Memcached and Aerospike, Redis is easier to deploy and manage. Aerospike, while highly efficient, is more complex to set up.

The initial setup of Redis is very straightforward and user-friendly. Deploying Redis takes about thirty seconds, making it quick and efficient.

Implementation can be done in-house using AWS ElasticCache or Docker to run Redis on Kubernetes, depending on cost and environmental factors.

We use Kafka for inter-process communication, but Redis is used for thread intercommunication due to its PubSub capabilities.

I recommend Redis as it provides an easy-to-use caching solution with beneficial PubSub features. 

It's excellent for startups or new projects with many components needing coordination. However, for more advanced messaging or larger data volumes, Redis might not be the best fit. 

I rate Redis a nine out of ten.

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 primarily use Redis as a cache to store the most requested files, folders, and URLs. This makes retrieval fast and has minimal latency.

Redis is a simple service that does what it promises. We use it through AWS, and it's not managed by us. There is no operational overhead thanks to Amazon. It is highly available, reliable, and functions exactly as expected, eliminating the need to reinvent the wheel with cache.

There is room for AWS to provide more options for server types or a way to configure more or less memory for them.

I have been using Redis for about four years.

Redis is 100% stable for our needs. We haven't experienced any complaints or issues related to stability.

AWS allows you to change the cluster size for Redis easily. However, I am unsure if horizontal scaling is possible.

Using AWS for Redis, the setup involves going through a user-friendly UI, making the process simple and straightforward. After setup, you get an endpoint, and it's ready to use.

We use Redis through AWS, so we pay related costs monthly as specified by Amazon.

I rate Redis a ten out of ten. There might be some improvement needed by allowing more configuration options regarding resources available for the servers.

I use Redis for data deduplication or identifying duplicate records I receive. I have a very basic usage with Redis, where I insert a key value record.

The solution is fast, provides good performance, and is not too expensive. Although installing it locally would probably be cheaper, I don't want the hassle. For the functionality I need, Redis gives me what I want at the moment.

The solution's pricing for a local installation is very expensive.

I have been using Redis for three years.

I haven’t faced any issues with the solution’s stability.

Azure allows Redis to scale. If I want, I can increase the resources allocated for this service.

I'm using the solution as an Azure cloud service with no installation involved.

The solution does what I need, and I have no issues with it. Since I didn't install Redis and don't need to maintain it, the service saves me a lot of time.

Overall, I rate the solution ten out of ten.

I use Redis mostly to cache repeated data that is required. If I'm using a user wallet address, I don't need to call it all the time from the database. I do the cache using the solution.

The solution allows you to create a message of application publishing and messaging the application in other services. It helps a lot when I work with the microservice architecture.

I have been using Redis for four years.

I haven’t faced any stability issues with the solution.

I have never faced any issues with the solution’s scalability.

The solution is easy to set up and has very clear documentation.

To deploy Redis, you need knowledge about JavaScript, programming, and how data structures are stored. It takes around five to ten minutes to deploy the solution.

With Redis, I can create lists and key-value pairs. The solution also provides many features for storing data in cache. Storing data in memory using Redis is faster than using traditional databases like Postgres or MySQL.

If you are communicating with the services, you can use the solution's Pub/Sub capabilities to send messages, store data in cache, and share it with other microservices. The solution's data persistence model has greatly benefited our resilience, especially when storing any key-value pair.

You can install the solution on the local machine or cloud servers like AWS or Google Cloud. I would recommend Redis to other users.

Overall, I rate the solution a nine out of ten.

Our organization's main use case for Redis is to store and load static content for our multi-client products.

The best thing about Redis is its ability to handle large amounts of data without frequently hitting the database. You can store data in temporary memory, especially for high-volume data. 

The tool should improve by increasing its size limits and handling dynamic data better. We use the client ID or associate it with a key for static content. The solution will not be easy for a beginner. Unless you understand SQL data, it will be difficult to understand and use Redis. It also needs to be user-friendly. 

I haven't contacted technical support yet. 

The tool is open-source. There are no additional costs. 

If you have a large amount of non-dynamic data that needs to be delivered to the client, you should use Redis. I don't think that it will support AI initiatives since it doesn't support continuous data. I rate the overall solution a seven out of ten. 

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.

Sometimes, Redis is used as a cache and sometimes as the main database.

Redis is a simple, powerful, and fast solution.

Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application.

I have been using Redis for three years.

I rate Redis a seven or eight out of ten for stability.

In our team, around 20 to 25 engineers are using the solution.

I rate Redis a nine or ten out of ten for scalability.

The solution's technical support team was quite knowledgeable and fast.

Positive

We previously used other solutions like DynamoDB, Elasticsearch, and Postgres for different use cases. We switched to Redis because maintaining the cluster for Elasticsearch was very complex and a lot of work. Also, the other solutions were very, very expensive.

The solution’s initial setup is easy.

Since we're using the AWS self-managed version, Redis can be deployed very fast if you go through the console. If you do an infrastructure, its setup will take longer. But if you just want to play with it and set it up quickly, it can be done in 10 to 15 minutes or less.

The solution's pricing is good compared to other databases doing the same thing. It might be cheaper to use Redis in some cases and not in others. Redis is not an overpriced solution.

Redis is deployed on-cloud in our organization.

When it started, Redis had a very simple structure, but now it has a lot of powerful data structures. Users should investigate because they can use other things for their data structure. Redis has more new use cases. Users must consider that Redis is single-threaded, which might take a toll on them when they write to Redis. This might be an issue if you need very high throughput with writes.

Overall, I rate Redis a nine out of ten.