Microsoft Azure Cosmos DB Reviews

We are strict users of Microsoft. We use it to deal with huge amounts of data. It's like Databricks and it's structured. All of the sites we have are stored in Cosmos DB.

The solution's enhanced performance is its most valuable aspect.

The product is very stable.

We've found the solution to be scalable.

The solution is extremely user-friendly and easy to navigate.

The initial setup is quick and easy.

I cannot recall finding any missing features. Everything we need is pretty much there.

It would be ideal if we could integrate Cosmos DB with our Databricks. At this point, that's not possible.

I've used the solution for one year at this point.

The solution is stable. There are no bugs or glitches. It doesn't crash or freeze. It's quite reliable.

The scalability of the solution is very good. If a company wants to expand it, it can.

Currently, we have about 80 users on the solution within our company.

We've had a year of support and they've always been very good. They are helpful and responsive. We're satisfied with the level of support we receive when we need to contact them.

We've always used Microsoft. Previously, we just used a different deployment for Microsoft.

The installation is not complex. It's very straightforward and very easy. It hardly takes more than a few minutes to deploy the product. Everything happens very fast.

I handled the implementation myself. I did not need to hire a consultant or implementor to assist the company during the implementation process.

I am using the latest version of the solution.

Overall, I would rate the solution at an eight out of ten. I have always been very happy with its capabilities.

I would recommend the solution to other organizations.

We have a lot of use cases like for the web API backend where we have most of the processing jobs. It supports mobile, browser, and tablet. We have a single face application that interacts with the users and customers. It's backend and frontend architecture. For middleware, we use Kafka integration. We have PowerBI for reporting. 

I like the scalability. There aren't any constraints for posting in the geolocation. I also like the SQL architecture. 

The query is a little complex. SQL server should have more options. But the query should be better. 

The setup takes a bit of time but once it's done, it goes well. Backend developers need a bit of time to do the setup. 

I have been using DocumentDB for a little over a year. You can use the libraries that are available in the framework and connect to DocumentDB for your operation. 

It is stable but since we have multiple locations, if one point goes down, we can access another location easily. Most of the effort goes into the script and we use keywords to secure the accessibility and then we set up the encryption. Configuration takes time. We do it without self-script. If you do it manually, it is quite difficult but script does it in a better manner. 

We use our own documentation as our resource. Azure doesn't have many problems that we need to contact support except for developers who struggle to learn about SQL. They need training and to read up on the literature. 

We are satisfied with their support. 

It takes time to set up and understand. Since Azure has its own table, it's not so flexible. 

Before implementing, know now how to use DocumentDB. Understand your use case. From an architecture perspective, we have a use case where we wanted to use more SQ and we used DocumentDB as the first consideration. There isn't a better SQL than DocumentDB available. Cloud provides this type of platform.

The automatic performance is also very good. We did research on the internet and decided to go with DocumentDB. 

I would rate it an eight out of ten. Not a ten because there is what to be done for improvement. In the future, it should be simplified for developers so that it's not a hassle for them. There aren't many resources for SQL and DocumentDB. It may take time for more documentation to come out. 

In our accounting department, we store data in Azure Cosmos DB. We query and store IO-based data there.

I'm still in the process of exploring all the features. We're continuously adding and releasing data, so there are several apps that have been useful to me.

Since we're working in the cloud, it's not easy to incorporate all the features it supports. There is room for improvement in terms of integration with other vendors.

I have been using the solution for about a year.

Cosmos DB is a pretty stable solution. I would rate it a ten out of ten. 

The solution is pretty scalable. I would rate the scalability a ten out of ten.

If I had to rate it based on my initial usage, I would rate it around a seven.

The setup was done by the team. They followed a set of instructions and it was pretty straightforward. 

I would recommend understanding the underlying databases like Cosmos DB, but I don't think it supports Oracle. However, it does support various other databases. If it supports the databases you need, then go for it. If it doesn't support them, there's not much you can do.

Overall, I would rate the solution an eight out of ten. I'm not giving it a higher rating because it doesn't support all databases.

I was using Microsoft Azure Cosmos DB to correct some performance issues or see more about my environment.

The most valuable features of Microsoft Azure Cosmos DB were the general infrastructure, ease to use, and interface.

I have been using Microsoft Azure Cosmos DB for approximately three years.

The stability of Microsoft Azure Cosmos DB was good. I did not experience any bugs or glitches.

Microsoft Azure Cosmos DB is scalable.

During the time I was using Microsoft Azure Cosmos DB I did not use the support.

Microsoft Azure Cosmos DB was relatively easy to set up.

The price of Microsoft Azure Cosmos DB could be a bit lower.

I would recommend this solution to others.

I rate Microsoft Azure Cosmos DB a nine out of ten.

Our primary use case for this solution is to call confirmation details booked in Cosmos DB.

New features can be included and its stability can be further improved.

We have been using the solution for approximately five years.

The solution is stable.

The solution is scalable, and we intend to increase our usage.

I rate customer service and support a ten out of ten.

Positive

The initial setup is straightforward and can be done in a couple of hours.

We deploy and maintain the solution in-house.

I rate the solution a nine out of ten.

We use Microsoft Azure Cosmos DB for storing information from third-party systems in JSON format.

The product's most valuable feature is its ability to store documents and assets. You can execute a query over all the documents. It works reasonably fast. You can retain the original format of the document as received by the third-party system.

Microsoft Azure Cosmos DB's performance could be better. In large volumes of documents, the querying process becomes slow and complicated. It could be faster.

We have been using Microsoft Azure Cosmos DB for three years.

We have enterprise businesses as our customers for Microsoft Azure Cosmos DB.

The technical support services are good.

Positive

It is an easy-to-set-up and maintain product. The installation process involves integrating it into the pipeline. It takes a few minutes to an hour and requires five executives to implement it.

I rate Microsoft Azure Cosmos DB an eight out of ten. It is useful to store original data in original format.