Microsoft Azure SQL Database vs Redis comparison

"The stability is good and the performance is fantastic. Even when we try to do an inquiry into issues we can do it easily."

"Great auto-scaling and security features."

"The backup features are the most valuable."

"Emergency mode is quite useful."

"Microsoft Azure SQL Database is fairly easy to use and set up for our DBA teams, who use it for various applications and tools like RabbitMQ."

"The product's initial setup phase is very easy."

"I rate Microsoft Azure SQL Database 10 out of 10."

"Its technical support team is good."

"I use Redis mostly to cache repeated data that is required."

"The most valuable features of Redis are its ease of use and speed. It does not have access to the disc and it is fast."

"It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology."

"The online interface is very fast and easy to use."

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

"Redis is a simple, powerful, and fast solution."

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

"Redis is good for distributed caching management."

"Some issues with scalability."

"We need improvement in the latency between availability zones. The managed SQL MI does not allow us to control the zone it runs in, which affects latency."

"We haven't had any major issues that have prevented us from doing stuff fundamentally. For its implementation, sometimes, it is complicated to understand what your needs are. It would be good to have a few use cases that provide different cloud variations that match on-premise installations and show how they can be moved to the cloud a bit better."

"Azure SQL can improve by adding more machine learning features like other databases, such as Cassandra or Cosmos DB."

"Scalability is an issue because we can't upgrade to new versions due to hardware limitations."

"Microsoft Azure SQL Database would benefit from enhanced documentation, along with ongoing improvements to scalability and cost-effectiveness."

"I need something which is in one place so I can automate the Azure data factory, but it's a different tool. It's not easy and in one place, so I can't switch to the other tool and do something there, automate everything there in the on-prem infrastructure, and then have everything in the agent. I can just pick one packet and use it. However, I want to be able to click it and run it."

"The solution needs to improve its customer network, including its online support."

"If we use a lot of data, it will eventually cost us a lot."

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

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

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

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

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

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

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

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

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

"It is expensive. Snowflake and PostgreSQL are cheaper than this. Google is also cheaper than Azure. Its licensing is on a pay-as-you-go basis. It is based on usage and storage."

"Microsoft Azure SQL Database is not cheap."

"SQL Azure is an expensive solution."

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

"It requires a license. As compared to its competitors, such as Oracle, it is affordable and reasonable."

"I have an annual spend number, and it is in the hundred thousand dollar range. There are no additional costs to the standard licensing fees. Even though you have to look at the cost numbers of what you're going to be charged on a monthly basis, what you have to also remember is that your application may need a lot of rewriting and things like that. You get charged not just for the monthly costs but also for the transactions that occur. If your access to the data layer is not so efficient, your costs will go up because you're pulling far more data than you potentially need. These are hidden costs that nobody ever considers. If your application is not written very efficiently, you may actually increase your costs over on-prem versus cloud."

"Redis is an open-source product."

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

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

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

"Redis is not an overpriced solution."