We just raised a $30M Series A: Read our story

Microsoft Azure Cosmos DB OverviewUNIXBusinessApplication

Microsoft Azure Cosmos DB is #1 ranked solution in top Managed NoSQL Databases. IT Central Station users give Microsoft Azure Cosmos DB an average rating of 8 out of 10. Microsoft Azure Cosmos DB is most commonly compared to Amazon DynamoDB:Microsoft Azure Cosmos DB vs Amazon DynamoDB. The top industry researching this solution are professionals from a computer software company, accounting for 24% of all views.
What is Microsoft Azure Cosmos DB?

DocumentDB is a fully managed NoSQL database service built for fast and predictable performance, high availability, elastic scaling, global distribution, and ease of development. As a schema-free NoSQL database, DocumentDB provides rich and familiar SQL query capabilities with consistent low latencies on JSON data - ensuring that 99% of your reads are served under 10 milliseconds and 99% of your writes are served under 15 milliseconds. These unique benefits make DocumentDB a great fit for web, mobile, gaming, and IoT, and many other applications that need seamless scale and global replication.

Microsoft Azure Cosmos DB was previously known as Microsoft Azure DocumentDB, MS Azure Cosmos DB.

Microsoft Azure Cosmos DB Buyer's Guide

Download the Microsoft Azure Cosmos DB Buyer's Guide including reviews and more. Updated: November 2021

Microsoft Azure Cosmos DB Customers

American Cancer Society, Exxon Mobil, Symantec

Microsoft Azure Cosmos DB Video

Pricing Advice

What users are saying about Microsoft Azure Cosmos DB pricing:
  • "Cosmos should be cheaper. We actually intend to stop using it in the near future because the price is too high."
  • "There is a licensing fee."
  • "For the cloud, we don't pay for the license, but for the on-prem versions, we do pay."

Microsoft Azure Cosmos DB Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
KS
Associate Director at a financial services firm with 10,001+ employees
Real User
Top 5Leaderboard
Provides single-digit millisecond response times but struggles with large amounts of data

Pros and Cons

  • "I would recommend Cosmos. It made our lives a lot easier. There's not a big learning curve in order to understand the structure and how to use it."
  • "We should have more freedom to tweak it and make our own queries for non-traditional use-cases."

What is our primary use case?

We have a database stored on Microsoft Azure where we fetch records and validate them against the application data that is displayed. We use it as a backend in an application to store data.

Within our organization, there are around 500 people using this solution.

What is most valuable?

There's no specific feature of Cosmos. Basically, we try to query the database. Since it's unstructured data, all the related fields are stored as a single JSON. You don't have to go ahead and hit multiple tables, or multiple containers. Instead, you get all of those things, relationally, stored in a nested JSON — in one single container itself. This way, you don't have to go back and forth to different tables. There are pros and cons with this feature, but often it makes things easier for us.

I am impressed with the TTL (time to live feature) of Cosmos. If we need to perform a manual addition to a container, we just need to configure the time to live. And then based on that, it can be deleted.

What needs improvement?

We should have more freedom to tweak it and make our own queries for non-traditional use-cases.

For how long have I used the solution?

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

What do I think about the stability of the solution?

Cosmos should be more stable. Sometimes we fetch more than 60,000 records at a time. When we try to fetch large amounts of data, sometimes it breaks-down, requiring us to rescale it. Overall, performance-wise, it needs to be a little more stable. 

How are customer service and technical support?

I personally haven't had contact with the technical support. Our solution architects deal with support. 

How was the initial setup?

I wasn't involved in the initial setup. We have a DevOps team that was responsible for handling the installation. We are just leveraging it for developmental purposes.

What's my experience with pricing, setup cost, and licensing?

Cosmos should be cheaper. We actually intend to stop using it in the near future because the price is too high — and because of the stability issues. 

What other advice do I have?

Overall, on a scale from one to ten, I would give this solution a rating of seven. Aside from the scalability issues, we haven't experienced any other issues. 

I would recommend Cosmos. It made our lives a lot easier. There's not a big learning curve in order to understand the structure and how to use it. We were good to go with only one container. Anybody who is new can learn quickly.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
RP
Cloud Architect at a manufacturing company with 10,001+ employees
Real User
Top 20Leaderboard
Has good scaling abilities and good automatic performance

Pros and Cons

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

What is our primary use case?

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. 

What is most valuable?

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

What needs improvement?

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. 

For how long have I used the solution?

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. 

What do I think about the stability of the solution?

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. 

How are customer service and technical support?

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. 

How was the initial setup?

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

What other advice do I have?

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. 

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Find out what your peers are saying about Amazon DynamoDB vs. Microsoft Azure Cosmos DB and other solutions. Updated: November 2021.
554,382 professionals have used our research since 2012.
KR
Information Technology Administrator at a tech services company with 51-200 employees
Real User
Top 5Leaderboard
Straightforward to set up, stable, easy to use, and well-compliments a solution that includes a relational database

Pros and Cons

  • "Cosmos DB is stable and easy to use."
  • "Better documentation on how to integrate with other components would be helpful because I was struggling with this."

What is our primary use case?

Cosmos DB is a non-relational, NoSQL database. We are a solution provider and we implement this product for our clients. It is used for integrating and managing unstructured data such as videos, pictures, and other big objects that you cannot include in a standard database tablet. It is made for these kinds of activities.

Some of our customers include banks, where together with their main relational database, it provides a place for keeping track of unstructured data. The relational database is used to store the regular data, whereas Cosmos DB stores what is unstructured.

I also use this product for my own purposes.

What is most valuable?

Cosmos DB is stable and easy to use.

What needs improvement?

Better documentation on how to integrate with other components would be helpful because I was struggling with this. For example, I had trouble finding information on how to integrate with other Microsoft components. Also, consider a situation where you want to use Cosmos DB to manage the uploading of data to your website. Information on how to do things like this should be readily available.

For how long have I used the solution?

I have been using Microsoft Azure Cosmos DB for less than a month.

What do I think about the stability of the solution?

Cloud-based solutions like Cosmos DB are quite stable.

What do I think about the scalability of the solution?

This is a scalable product. When I originally used it on the cloud, Microsoft Azure, I tried changing a lot of things such as increasing the memory to see how it performed. The response was quite good. 

How are customer service and technical support?

Technical support is good and they are responsive.

Which solution did I use previously and why did I switch?

Prior to Cosmos DB, was using MySQL, but it isn't a non-relational database.

How was the initial setup?

The initial setup is straightforward. It was complete in about five minutes.

What about the implementation team?

I deployed it myself.

What's my experience with pricing, setup cost, and licensing?

There is a licensing fee.

What other advice do I have?

This is a good product and I recommend it, especially in cases where people want to keep their information outside of the organization and on the cloud.

I would rate this solution a nine out of ten.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
KG
Associate Manager at a consultancy with 501-1,000 employees
Real User
Top 5Leaderboard
Very user-friendly, easy to set up, and scalable

Pros and Cons

  • "The solution is extremely user-friendly and easy to navigate."
  • "It would be ideal if we could integrate Cosmos DB with our Databricks. At this point, that's not possible."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

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.

Which solution did I use previously and why did I switch?

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

How was the initial setup?

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.

What about the implementation team?

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
LN
Enterprise Cloud Architect at a financial services firm with 10,001+ employees
Real User
Top 5Leaderboard
Useful for many use cases, 99.9% availability, and easy to install

Pros and Cons

  • "Its wide support to the ecosystem is valuable. We can use this database with a lot of use cases, and that's one of the reasons why we prefer it. We have a lot of vendors, databases, and use cases, and wherever possible, we are trying to standardize databases. It is also secure."
  • "At this stage, we would like more enterprise support. We use MongoDB a lot, and we're trying to get rid of MongoDB. So, I would like to see more features in the Cosmos DB API for MongoDB space."

What is our primary use case?

We mostly use it for NoSQL use cases. We use it for web applications, mobile applications, and social applications in the financial sector.

It is deployed on-premises and on the cloud, and we are using its latest version but not the one in the public review.

What is most valuable?

Its wide support to the ecosystem is valuable. We can use this database with a lot of use cases, and that's one of the reasons why we prefer it. We have a lot of vendors, databases, and use cases, and wherever possible, we are trying to standardize databases. It is also secure.

What needs improvement?

At this stage, we would like more enterprise support. We use MongoDB a lot, and we're trying to get rid of MongoDB. So, I would like to see more features in the Cosmos DB API for MongoDB space.

For how long have I used the solution?

I have been using this solution for almost two years.

What do I think about the stability of the solution?

It is stable. It has 99.999% availability, and it is backed by SLAs.

What do I think about the scalability of the solution?

We have thousands of users.

How are customer service and technical support?

We use the cloud version and the on-prem version. We have our on-prem database engineering team. For the cloud, we are okay with their support.

Which solution did I use previously and why did I switch?

We use MongoDB a lot, and we're trying to get rid of MongoDB.

How was the initial setup?

It is easy to install. I tried it in a testing environment, and it was easy. Database experts should be able to do it easily.

What's my experience with pricing, setup cost, and licensing?

For the cloud, we don't pay for the license, but for the on-prem versions, we do pay.

What other advice do I have?

I would rate Microsoft Azure Cosmos DB a nine out of 10.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate