Microsoft Azure SQL Database vs Redis comparison

"The stability of the solution is very good."

"Overall, Azure SQL has been great. The ease of deployment and scalability are significant reasons we push our larger clients to Azure. We could throw the kitchen sink at the thing if we wanted."

"They have good documentation. It's concentrated information."

"The backup solution in Azure is great, the firewall settings in SQL are very easy to use and work very well. Additionally, the turning process is very good and has improved the SQL services and queries."

"The solution has become easier to use over time and it's also reasonably priced."

"The most valuable aspect of Microsoft Azure SQL Database is its accessibility."

"It's the type of product that doesn't need much technical support assistance as it works seamlessly."

"The tool set is familiar since I've used SQL Server on-premises for quite a few years."

"The solution's technical support team is good...The solution's initial setup process was straightforward."

"The ability to fetch and save data quickly is valuable."

"I find Redis valuable primarily for its caching capabilities, particularly in handling cache requests effectively. Its simplicity in managing key-value pairs for caching is one of its strengths, making it a preferred choice over more complex databases like MongoDB for specific use cases. However, I haven't explored Redis extensively for managing complex data structures beyond caching, as MongoDB might be more suitable for such scenarios."

"Redis provides an easy setup and operation process, allowing users to quickly connect and use it without hassle."

"The solution is fast, provides good performance, and is not too expensive."

"What I like best about Redis is its fast and easy use. It has interesting algorithms like HyperLogLog and provides useful features. It's also good for implementing scalable rate limiting."

"Redis acts as an in-memory search tool that improves the speed of operations."

"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."

"There is so much information that it becomes confusing at times. The information can be more friendly. They could also provide additional training, especially at the beginning."

"We've noticed an unexpected increase in the cost of running the server over the past few months."

"I would like to the solutions scalability to be improved."

"SQL Azure could improve by adding more features."

"There needs to be a hybrid model for situations where not all customers want a cloud-based SQL solution."

"Lack of flexibility for developers in terms of performance assistance."

"Its compatibility with existing applications can be improved. Its compatibility is currently a little bit imbalanced."

"If it's a transitional system, there is a lot of reporting, so the solution becomes a bit slow when it's churning out tons of data, but it's good for a mid-sized application"

"For the PubSub feature, we had to create our own tools to monitor the events."

"In future releases, I would like Redis to provide its users with an option like schema validation. Currently, the solution lacks to offer such functionality."

"Redis should have an option to operate without Docker on a local PC."

"There are some features from MongoDB that I would like to see included in Redis to enhance its overall efficiency, such as the ability to perform remote behaviour. MongoDB is more efficient in handling updates than deletions and is quicker in processing updates, but it can be slower regarding deletions. This can sometimes pose a challenge, especially when dealing with large datasets or frequent data manipulations that involve deletions. In such cases, I often rewrite columns or update values instead of directly deleting data, as it can be more efficient."

"The development of clusters could improve. Additionally, it would be helpful if it was integrated with Amazon AWS or Google Cloud."

"Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud."

"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."

"Redis presents a single point of failure and lacks fault tolerance."

"The price in general of Azure SQL could improve."

"If we use a smaller or free-sized Microsoft Azure SQL Database, it is extremely cost-effective and much cheaper than on-premise enterprise licenses, which are expensive."

"I would like it to be cheaper, but comparatively, it is reasonably priced."

"It is reasonable."

"I recommend considering a pay-as-you-go pricing model initially."

"The pricing is actually complicated, and that is probably one downside of it. In some respects, although we can plan for the costs on a month-by-month basis, we are finding it hard to project our costings for it. Fundamentally, Microsoft is offering two pricing models, and it is challenging to understand the differences between the two. We're basically on the DTU model at the moment. That may change in the future as the size grows, but it is one of those things that we'll end up monitoring as we progress. At the moment, to get a reasonable response, generally, the price is a little high for us, but it is one of those things for which we know that we can do improvements on our code. So, it is not just the service that's the problem; it is some of the things that we need to do as well."

"I find that they are relatively expensive, especially when compared to AWS, where the prices are notably lower."

"Offers options for paying the license on a yearly or a monthly basis."

"Redis is an open-source solution. There are not any hidden fees."

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

"We saw an ROI. It made the processing of our transactions faster."

"Redis is not an overpriced solution."

"Redis is an open-source product."