Microsoft Azure Cosmos DB Reviews

We have a massive quantity of data that we need to maintain, and we can't put it in a relational database since we need all of the data and want it to be queried quickly.

We maintain it in non-relational databases such as Microsoft Azure Cosmos DB.

It's not a specific feature that I value, but the scalability of this system is the most impressive aspect.

The UI should be improved since if you provide the option to query directly when signing into the Azure portal, it makes no sense if you have such a poor UI for querying that you can't even feed the reports correctly. 

It should offer a simple user interface for querying Microsoft Azure Cosmos DB.

I have been using Microsoft Azure Cosmos DB for a long time, almost forever.

We are always working with the latest version.

It's fairly stable. I have no complaints about the stability of Microsoft Azure Cosmos DB.

Microsoft Azure Cosmos DB is fully scalable.

Users do not connect to Microsoft Azure Cosmos DB directly. Our APIs connect to Microsoft Azure Cosmos DB and are then used by the front end. 

Estimating the number of users is impossible.

Because our complete setup is in Microsoft, we have access to the most premium Microsoft assistance, available 24 hours a day, seven days a week. We have never had a problem with technical support.

The initial setup is straightforward.

The RU's use case determines our license fees. It fluctuates based on how many RUs we have. It's not a fixed-line.

Because our whole solution was hosted on Azure, this was the default option for us. We didn't look into any other possibilities.

I would recommend this solution to others who are interested in using it.

I would rate Microsoft Azure Cosmos DB a seven out of ten.

I use Microsoft Azure Cosmos DB for data engineering.

Microsoft Azure Cosmos DB is fast, and its performance is good compared to normal SQL DB.

Sometimes, the solution's access request takes time, which should be improved.

I have been using Microsoft Azure Cosmos DB for one year.

Microsoft Azure Cosmos DB is a stable solution.

Microsoft Azure Cosmos DB is a scalable solution. More than 100 users use the solution in our organization.

The solution's initial setup is straightforward.

The solution's deployment time depends on how complex the job is. Learning-wise, it takes a few weeks to get your hands on, and then you can get started from there. The solution was implemented through an in-house team in our organization.

Microsoft Azure Cosmos DB is deployed on-cloud in our organization.

I would recommend Microsoft Azure Cosmos DB to other users.

Overall, I rate Microsoft Azure Cosmos DB a seven out of ten.

We handle JSON data and it is compatible with Microsoft Azure Cosmos DB. 

I have found Microsoft Azure Cosmos DB different from other SQL databases like RDBMS. It is non-SQL and helps to manage and manipulate data from the coding, rather than direct data and complex queries. It is quite flexible and offers a complete concentration on the coding part only. Even if one lacks expertise in complex queries, JSON and Microsoft Azure Cosmos DB are quite compatible with each other and makes the database options more enhanced and easy to operate. The additional SQL features allow you to go to Azure's portal and get the queries solved. 

I have been a devoted Microsoft fan, but Redis DB's memory caching capabilities are really making progress. Even if Cosmos DB is continuously improving and is quite advanced in the field of internal memory optimization, I would still recommend Redis DB to a customer. My dilemma still lies in the price of both solutions. I believe if Redis DB is superior and pricier than Cosmos DB, customers will be reluctant to use Redis DB.  

Memory streaming and various optimizations contribute to higher costs but also increased speed. Currently, there's nothing specific I can pinpoint that needs to be added – I haven't made any purchases yet. However, I am inclined to recommend working with it. 

I have worked with Microsoft Azure Cosmos DB for one year.

It is a stable solution. I rate the stability a nine out of ten.

It is a scalable solution. I rate the scalability a nine out of ten. 

We haven’t faced any issues that would make us contact service support or raise tickets

Positive

The solution's initial setup is easy. The deployment took almost one day. We migrated the services from the CRM system, converted them into JSON, and deployed it. I would rate the initial setup an eight out of ten. 

If a customer needs to store JSON data, and the solution doesn't require complex structure and reporting like BI reports and RDBMS, opting for a NoSQL database could be ideal. NoSQL databases are suitable when data isn't structured in a relational manner and when extensive normalization isn't a priority. For efficiently handling JSON data for UI purposes or other needs, a NoSQL database like Cosmos DB is the way to go.

However, in the NoSQL landscape, various options like Redis DB, CouchDB, MongoDB, and Cosmos DB exist. If a preference leans towards Microsoft technologies, then Cosmos DB becomes a logical choice. Comparing Cosmos DB with alternatives like Redis DB is advisable before making a final decision. Thus, my typical recommendation involves considering these factors.

I would Cosmos DB a nine out of ten.

Microsoft Azure Cosmos DB has helped improve the search result quality of our customers' organization. The customer gave us the feedback that they are able to easily find the data they are looking for. It is very quick. That is the best feedback. They have a large amount of data, and they can find it quickly.

Our customer is very satisfied with it. Our branch does not use it yet. We used it for a customer, and the customer is very satisfied so far.

There are no particular factors that need improvement. There is a little bit of a learning curve with scaling workloads, but it works smoothly.

I am still learning it and have only used it for one application so far. 

No issues have been reported regarding the stability. It is very fast.

There was a little bit of a learning curve with scaling workloads, but overall, it went smoothly.

I have not had any challenges. However, the configuration done in a session at Microsoft Ignite looked complicated. It would be a bit challenging to do the same configuration. 

There is a little bit of a learning curve. The onboarding process for the team took about two weeks.

The only feedback the customer gave us was that it was way cheaper than they expected. 

The customer had a high budget, but it turned out to be a little bit cheaper than what they expected. I am not sure how much they have spent so far, but they are satisfied with the pricing.

I would recommend this product. I would like my organization to develop and explore it further. I would rate Microsoft Azure Cosmos DB an eight out of ten.

The company is using Microsoft Azure Cosmos DB for business intelligence information, specifically for demand management.

What I like about Microsoft Azure Cosmos DB is that it's easy to do data ingestion and use the data in different applications. If you talk about business intelligence such as the Power BI tool, it's easy to connect because both are Microsoft products. With Microsoft Azure Cosmos DB, it's easy to connect and do data ingestion.

At the moment, because I'm still new in terms of using Microsoft Azure Cosmos DB, I don't have any feedback regarding areas for improvement in the product. So far, it has met all the expectations and needs of my company.

It would be nice to have more options to ingest the data, for example, more file options or more search options. Currently, you can use JSON, but if there were other file types you can use for data ingestion, that would be nice. This is the additional feature I'd like to see in the next release of Microsoft Azure Cosmos DB.

I've been using Microsoft Azure Cosmos DB for the past six months.

Microsoft Azure Cosmos DB is a stable product.

Microsoft Azure Cosmos DB is a scalable product.

We have a partnership with Microsoft, so the response time of the technical support team for Microsoft Azure Cosmos DB is really good at the moment.

Microsoft Azure Cosmos DB was easy to set up.

I've been using Microsoft Azure Cosmos DB, a cloud DB solution. It's deployed in a cloud environment, on a public cloud with security for ourselves.

My company is a partner of Microsoft and also a reseller.

My advice to people looking into implementing Microsoft Azure Cosmos DB is that it would be good for them to use, specifically if they are looking for a NoSQL database to ingest the data and do data discovery using the data in a BI tool. It's easy to ingest the data and work with the data in Microsoft Azure Cosmos DB and understand that, because it is not a SQL database, which means it's not as structured. You can add data, and then do a data discovery, and use it the best way for you. I would recommend Microsoft Azure Cosmos DB.

My rating for Microsoft Azure Cosmos DB is eight out of ten.

We use Microsoft Azure Cosmos DB for faster databases.

The most valuable feature of the solution is that it is scalable with multiple master files. The performance of the solution is also good.

Microsoft Azure Cosmos DB's pricing model is complicated, which people don't understand. So, the pricing model should be improved.

I have been using Microsoft Azure Cosmos DB for five years.

Microsoft Azure Cosmos DB is a stable solution.

Microsoft Azure Cosmos DB is a highly scalable solution, and 15 to 20 people use the solution in my organization.

I rate Microsoft Azure Cosmos DB’s technical support an eight out of ten. They do take some time to get to the root of a problem.

Positive

The initial setup is straightforward and needs a few tools to upload.

We have had an ROI with the solution.

The pricing model of Microsoft Azure Cosmos DB is a bit complex.

We are using Microsoft Azure Cosmos DB as a cloud-based solution. Two admins and one manager are required for the deployment and maintenance of the solution.

New users must keep an eye on its pricing models and configure them properly.

Overall, I rate Microsoft Azure Cosmos DB an eight out of ten.

We use different Azure services in the development of our solutions. Some of the services we use are Azure Cognitive Services, ADB2C, and SignalR.

For most of the solutions, we use a mixture of Azure SQL Database and Cosmos DB. We use Cosmos DB when the data size is huge, and we need to scale.

Currently, only two people in my organization are working on this solution: one developer and myself. In the future, I think once the system gets deployed, we will have thousands of users. 

Cosmos DB solves certain problems that relational databases cannot handle. It's a multimodal NoSQL database, and it's very scalable. One of the nice features is the ability to auto-scale, plus Cosmos DB's API is easy to use. 

I hope they improve the service. Before last year, improvements on Cosmos DB were very slow. I didn't see many changes in the functionality.

I have been using this solution for four years.

I would rate the stability as nine out of ten.

It's very scalable and fast.

I had developer support with Microsoft Azure. I faced a problem a few years ago, and they helped me solve it.

Positive

It's very easy to set up Cosmos DB. First, you decide what type of API to use, like SQL, Graph, etc., or if you want support for MongoDB or Cassandra APIs. I usually use SQL API. Once you choose the type of API, you create an account and a database. Then you create containers, and you can easily write queries.

I believe there will be a return on investment because using cloud solutions will remove all capital expenses. Cosmos DB's auto-scaling options minimize the cost. Choosing "pay as you go" services cuts costs especially when users are not using the system.

I hope Microsoft lowers the cost further.

We evaluated MongoDB and Cassandra, 

I would rate this solution as eight out of ten.

The APIs are improving and are easy to use. It is easy to set up a new database, and the auto scalability and support for different models are good features.

I use Cosmos DB for geolocation identification.

If you pass by a market on the street, it sends me your location. My application will then send you a personalized notification about relevant products you can buy at the market.

The best feature is the velocity of making queries. 

I would like to see better documentation for this solution. 

The pricing of the solution should be reduced. 

I have been using Cosmos DB for one year. 

I would rate stability an eight out of ten. 

I would rate scalability a five out of ten. 

I would rate technical support a ten out of ten. 

The initial setup is straightforward. It's very easy to start a function or application with Azure. 

The solution is very expensive. 

I would overall rate the solution an eight out of ten.