Azure Cosmos DB vs. Redis Cloud vs. Azure SQL Database

Like any NoSQL database, whether it's MongoDB or not, it's best suited for unstructured data. It's also well suited for storing raw data before processing it and performing any type of ETL on the data.

Incentivized

Redis Cloud is very well suited for scenarios where fast data access is required or somewhat unstructured data needs to be stored. For us, it has worked very well for user session storage. However, if you have large amounts of structured data that is not frequently accessed, Redis is not the solution and a traditional relational database is likely more appropriate.

Incentivized

We have found it's a great alternative for making older legacy applications work with online databases instead of only on-premises databases. We've converted over a dozen applications this way, and it has allowed our clients to have a distributed workforce using their applications without incurring the expense of a complete application rewrite.

Incentivized

• Scalable Instantly and automatically serverless database for any large scale business.
• Quick access and response to data queries due to high speed in reading and writing data
• Create a powerful digital experience for your customers with real-time offers and agile access to DB with super-fast analysis and comparison for best recommendation

Incentivized

• Ease of setup and deployment via Heroku
• Reliability and splicity
• Fair pricing

Incentivized

• Maintenance is always an issue, so using a cloud solution saves a lot of trouble.
• On premise solutions always suffer from fragmented implementations here and there, where several "dba's" keep track of security and maintenance. With a cloud database it's much easier to keep a central overview.
• Security options in SQL database are next level... data masking, hiding sensitive data where always neglected on premise, whereas you'll get this automatically in the cloud.

Incentivized

• Expensive, so be careful of the use case.
• We had a thought time migrating from traditional DBs to Cosmos. Azure should provide a seamless platform for the migration of data from on-premises to cloud.

Incentivized

• The only area of improvement I have found is the documentation is sometimes lacking and could be a little more comprehensive.

Incentivized

• One needs to be aware that some T-SQL features are simply not available.
• The programmatic access to server, trace flags, hardware from within Azure SQL Database is taken away (for a good reason).
• No SQL Agent so your jobs need to be orchestrated differently.
• The maximum concurrent logins maybe an unexpected problem.
• Sudden disconnects.
• The developers and admin must study the capacity and tier usage limits https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits otherwise some errors or even transaction aborts never seen before can occur.
• Only one Latin Collation choice.
• There is no way to debug T-SQL ( a big drawback in my point of view).

Incentivized

It's efficient, easy to scale, and works. We do have to do a bit of administration, but less now than when we started with this a couple of years ago. Microsoft continues to improve its self-management capability.

Incentivized

This is best solution as a DBA one could expect from a service provider and as a cloud service, it removes all your hassles.

Incentivized

It has very good compatibility and adaptability with other APIs and developers can safely create new apps because it is compatible with various tools and can be easily managed and run under the cloud, and in terms of security, it is one of the best of its kind, which is very powerful and excellent.

Incentivized

The interfaces are intuitive once you are familiar with all the functions. The ability to use different tools to interact with the platform, such as directly via a browser or code editors such as VS Code or Visual Studio is a great option and allows for integrating withn the project and other testing and developing tools.

Incentivized

Microsoft is the best when it comes to after-sales support. They have a well-structured training and knowledge base portal that anyone can use. They are usually quick to respond to cases and are on point for on-call support. I have no complaints from a support standpoint. Pretty happy with the support.

Incentivized

We give the support a high rating simply because every time we've had issues or questions, representatives were in contact with us quickly. Without fail, our issues/questions were handled in a timely matter. That kind of response is integral when client data integrity and availability is in question. There is also a wealth of documentation for resolving issues on your own.

Incentivized

Cosmos DB is unique in the industry as a true multi-model, cloud-native database engine that comes with solutions for geo-redundancy, multi-master writes, (globally!) low latency, and cost-effective hosting built in. I've yet to see anything else that even comes close to the power that Cosmos DB packs into its solution. The simplicity and tooling support are nice bonus features as well.

Incentivized

I've used Heroku Redis and RedisToGo. Redis Cloud has the best free/developer plan, and we have never had an issue.

Incentivized

We moved away from Oracle and NoSQL because we had been so reliant on them for the last 25 years, the pricing was too much and we were looking for a way to cut the cord. Snowflake is just too up in the air, feels like it is soon to be just another line item to add to your Azure subscription. Azure was just priced right, easy to migrate to and plenty of resources to hire to support/maintain it. Very easy to learn, too.

Incentivized

• It's made managing raw data much easier
• It provides a way to maintain raw data at a low cost
• It's easy to massage the data

Incentivized

• Redis Cloud is very affordable and therefore the cost is negligible when compared to the benefits— immediate ROI with very little startup costs.

Incentivized

• Perfect for small and medium databases, being very cost effective.
• As a Platform as a Service, there is no concern about patches, upgrades and end of life.
• Be aware of security and network capabilities. The service cannot run in the VNET as Azure Virtual Machines do.