No more typing reviews! Try our Samantha, our new voice AI agent.
Divya Kumar - PeerSpot reviewer
CTO at UST Global
Real User
Sep 29, 2023
Impressive scalability and proficiency in database management
Pros and Cons
  • "It is one of the simpler databases to work with in terms of code management, tracking, and debugging due to its straightforward data storage and retrieval mechanisms."
  • "There is room for improvement in their customer support services."

What is our primary use case?

Our current project primarily relies on the file system to handle incoming source tests. Within this setup, we capture both metadata and result data from these tests. We extract metadata information from these files and store it in Azure Cosmos DB and we have several software services in place to facilitate this process.

What is most valuable?

It is one of the simpler databases to work with in terms of code management, tracking, and debugging due to its straightforward data storage and retrieval mechanisms.

What needs improvement?

There is room for improvement in their customer support services.

For how long have I used the solution?

In one of our recent projects, we stored metadata information and log data within Cosmos DB.

Buyer's Guide
Microsoft Azure Cosmos DB
October 2026
Learn what your peers think about Microsoft Azure Cosmos DB. Get advice and tips from experienced pros sharing their opinions. Updated: October 2026.
922,921 professionals have used our research since 2012.

What do I think about the stability of the solution?

It offers good stability capabilities.

What do I think about the scalability of the solution?

It offers impressive scalability, both in terms of throughput and storage. Its ability to scale dynamically allows us to align the database resources with the specific demands of our applications. Given its scalability and performance capabilities, we highly recommend it for use in large enterprises and organizations.

How are customer service and support?

There were instances where their customer support services were slow. As previously mentioned, when it came to setting up Azure Cosmos DB, not everyone was proficient in cost considerations, and our team lacked extensive prior experience. Our main support was provided by Microsoft's documentation and we were able to successfully navigate these challenges. I would rate it eight out of ten.

How was the initial setup?

The initial setup presented some challenges and required us to delve deeper into understanding the daily implications. Microsoft documentation proved to be a valuable resource in navigating this process.

What about the implementation team?

The initial setup, planning, and configuration took approximately one to two weeks to complete. The timeline for implementing the solution varied based on the specific use case and the discussions held with the client. We conducted regular reviews, documented our progress, and established a static attack system. Due to some design-related confusion, the overall implementation process was extended to about one to two months. Still, Cosmos DB and related components were set up within one to two weeks.

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

Its pricing structure is quite flexible. It operates on a pay-as-you-go model, which means the cost is directly tied to the resources you consume and the throughput you require. Initially, our expenses were relatively low because we didn't store a significant amount of data, but as our storage needs increased over time, our expenses naturally grew in proportion to the resources and capacity we used.

What other advice do I have?

Initially, we encountered some challenges in understanding it, as it wasn't as straightforward as managing an SQL Server database or setting up environments within Azure Data Factory and DevOps. This complexity is related to the fact that Cosmos DB offers a range of additional features and capabilities. Our initial difficulties could also be attributed to our team's limited prior experience with Cosmos DB. Considering these factors, I would rate our experience with it at an eight out of ten. Beyond these initial hurdles, we found it to be a valuable and capable solution.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Founder at Druansh
Real User
May 8, 2023
Globally distributed multi-model database service and robust stability
Pros and Cons
  • "It's highly scalable and supports consistency, security, and multiple security options."
  • "The biggest problem is the learning curve and other database services like RDS."

What is our primary use case?

Microsoft Azure Cosmos DB can be used for various purposes. The query language used for Cosmos DB is very similar to SQL, which gives it an advantage. It's a globally distributed multi-model database service, meaning it supports multiple data models, including documents, key-value pairs, graphs, and time series data models.

It's highly scalable and supports consistency, security, and multiple security options, such as REST and transit encryption. It also provides automatic support for these options. These are some top-level benefits of using Cosmos DB, making it a highly versatile and useful tool.

What is most valuable?

The multi-model database is the most valuable feature. 

What needs improvement?

One thing that concerns me is the cost, especially for smaller workloads. Cosmos DB is a little more expensive than other database services, particularly if you have tight-traffic models. However, it does have a few advantages, such as being a multi-model database. The biggest problem is the learning curve and other database services like RDS. 

Additionally, advanced analytics capabilities like real-time analytics and machine learning are not embedded in Cosmos DB. Vendor lock-in is a big concern. Cosmos DB is a proprietary database service offered by Microsoft that might not be compatible with other databases. 

For how long have I used the solution?

I have been using this solution for three years. I am using the latest version.

What do I think about the stability of the solution?

From a stability perspective, it's a pretty robust solution designed to offer high availability and fault tolerance. It provides multiple levels of redundancy and automatic failover to ensure data availability and reliability. 

What do I think about the scalability of the solution?

It is a scalable solution and has built-in backup and recovery capabilities. We developed it for one of our clients with around 20-25 users.

How are customer service and support?

When compared to other cloud platforms like GCP and AWS, I think Microsoft needs to work on its tech support.

How was the initial setup?

There is some learning curve associated with this software. It becomes relatively easy to implement if you have an expert to work with. 

The deployment process and maintenance depend on the size of the product and what you're trying to migrate. Generally, one cloud solution architect and one big data developer with Azure experience should be sufficient.

What was our ROI?

We could see an ROI. The whole idea of migrating to the cloud was for a better ROI, and we can see that now that the customer has moved to the cloud.

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

As your data grows, the licensing cost can be expensive.

What other advice do I have?

If your existing infrastructure already uses Microsoft services or is more of a Microsoft-dependent solution, it's best to be on Microsoft Azure cloud. This is because it integrates very well, and there is a smooth integration with other Microsoft products that are already running on our products. 

You can also leverage some of your existing licenses, saving you a lot of costs when you move to the cloud. That's one solution I would suggest for anyone who is moving from on-premise to the cloud. 

Overall, I would rate the solution an eight out of ten. 

Which deployment model are you using for this solution?

Private Cloud

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

Microsoft Azure
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Buyer's Guide
Microsoft Azure Cosmos DB
October 2026
Learn what your peers think about Microsoft Azure Cosmos DB. Get advice and tips from experienced pros sharing their opinions. Updated: October 2026.
922,921 professionals have used our research since 2012.
Raed Gharzeddine - PeerSpot reviewer
Technical advisor and software architect at Technical advisor and software architect
Real User
Dec 23, 2022
Provides auto-scalability and is a multimodal NoSQL database
Pros and Cons
  • "One of the nice features is the ability to auto-scale"
  • "I hope they improve the service. Before last year, improvements on Cosmos DB were very slow."

What is our primary use case?

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. 

What is most valuable?

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. 

What needs improvement?

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.

For how long have I used the solution?

I have been using this solution for four years.

What do I think about the stability of the solution?

I would rate the stability as nine out of ten.

What do I think about the scalability of the solution?

It's very scalable and fast.

How are customer service and support?

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

How would you rate customer service and support?

Positive

How was the initial setup?

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.

What was our ROI?

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.

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

I hope Microsoft lowers the cost further.

Which other solutions did I evaluate?

We evaluated MongoDB and Cassandra, 

What other advice do I have?

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.

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: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Aditya_Sharma - PeerSpot reviewer
Data Quality Engineer-III at Anheuser-Busch InBev
Real User
Oct 23, 2023
A stable solution that can be used for data engineering, but its access request takes time
Pros and Cons
  • "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."

What is our primary use case?

I use Microsoft Azure Cosmos DB for data engineering.

What is most valuable?

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

What needs improvement?

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

For how long have I used the solution?

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

What do I think about the stability of the solution?

Microsoft Azure Cosmos DB is a stable solution.

What do I think about the scalability of the solution?

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

How was the initial setup?

The solution's initial setup is straightforward.

What about the implementation team?

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.

What other advice do I have?

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.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Developer at NA
Real User
Aug 19, 2023
A solution that is scalable and easy to integrate new features into
Pros and Cons
  • "The solution is easy to use, and it is also easy to integrate with several things for database use cases."
  • "I would like the speed of transferring data to be improved."

What is our primary use case?

We normally use Cosmos DB for data storage.

What is most valuable?

There are a lot of security features that can be integrated with Cosmos DB. The solution is easy to use, and it is also easy to integrate with several things for database use cases.

What needs improvement?

I would like the speed of transferring data to be improved.

For how long have I used the solution?

I’ve been using it for two to three years, and I’m working on the latest version.

What do I think about the stability of the solution?

The solution is stable.

What do I think about the scalability of the solution?

The solution is very scalable. We have more than 1,000 users in our company.

How was the initial setup?

The initial setup is straightforward. We deploy Cosmos DB once or twice a quarter. We have three or four teams handling deployment and maintenance, which is about 38 members.

What about the implementation team?

We implement the solution in-house.

What was our ROI?

We are receiving an ROI with this solution.

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

Cost isn’t a big hurdle for us right now. The solution is not costly.

What other advice do I have?

I recommend Microsoft Azure Cosmos DB to anyone who wants to use it. If you are using Azure Stack, it is a good solution to use

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Technical Architect at LTI - Larsen & Toubro Infotech
Real User
Aug 14, 2023
Is quite flexible and offers a complete concentration on coding
Pros and Cons
  • "It is non-SQL and helps to manage and manipulate data from the coding, rather than direct data and complex queries."
  • "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."

What is our primary use case?

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

What is most valuable?

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. 

What needs improvement?

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. 

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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

How are customer service and support?

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

How would you rate customer service and support?

Positive

How was the initial setup?

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. 

What other advice do I have?

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.

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?

Disclosure: My company has a business relationship with this vendor other than being a customer. partner
PeerSpot user
RodrigoGalhardo - PeerSpot reviewer
CTO at Kultua
Real User
Jun 11, 2023
An application with great velocity to make queries
Pros and Cons
  • "The best feature is the velocity to make a query."
  • "A further simple application is required for Brazil."

What is our primary use case?

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.

What is most valuable?

The best feature is the velocity of making queries. 

What needs improvement?

I would like to see better documentation for this solution. 

The pricing of the solution should be reduced. 

For how long have I used the solution?

I have been using Cosmos DB for one year. 

What do I think about the stability of the solution?

I would rate stability an eight out of ten. 

What do I think about the scalability of the solution?

I would rate scalability a five out of ten. 

How are customer service and support?

I would rate technical support a ten out of ten. 

How was the initial setup?

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

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

The solution is very expensive. 

What other advice do I have?

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

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Joyal Benni - PeerSpot reviewer
Senior Consultant at ProArch
Real User
Apr 27, 2023
Is scalable with multiple master file and provides good performance
Pros and Cons
  • "The most valuable feature of the solution is that it is scalable with multiple master files."
  • "Microsoft Azure Cosmos DB's pricing model is complicated, which people don't understand."

What is our primary use case?

We use Microsoft Azure Cosmos DB for faster databases.

What is most valuable?

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

What needs improvement?

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

For how long have I used the solution?

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

What do I think about the stability of the solution?

Microsoft Azure Cosmos DB is a stable solution.

What do I think about the scalability of the solution?

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

How are customer service and support?

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.

How would you rate customer service and support?

Positive

How was the initial setup?

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

What was our ROI?

We have had an ROI with the solution.

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

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

What other advice do I have?

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.

Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
PeerSpot user
Nadeem-Ahmed - PeerSpot reviewer
Sr System Support Engineer at Premier Systems
MSP
Apr 18, 2023
Easy-to-use solution and highly scalable
Pros and Cons
  • "It is a scalable product."
  • "The initial setup was difficult."

What is our primary use case?

Primarily, people do not have a clear understanding of the cloud and cloud services. Customers are a little bit scared about taking their data onto the cloud, and they think and they assume that it is not safe. So we just make them understand that databases or services on the cloud are more secure than on-premises infrastructure.

What needs improvement?

The performance point can be improved because when we run a search query on our on-premises machine and develop connectivity, a response comes in. But sometimes, the response gets delayed, and it can be due to network latency or something else we are yet to figure out.

Performance and high availability are two features I want to be added in the next release because that is the basic requirement of customers. Mostly, we have customers with the bank and banking institutions, and they want their databases perfectly integrated with the high availability feature.

For how long have I used the solution?

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

What do I think about the stability of the solution?

It is a stable product. I would give it an eight out of ten. 

What do I think about the scalability of the solution?

It is a quite scalable product. I give it a nine out of ten. There are more than ten users using this product. 

How was the initial setup?

The initial setup was difficult. I would give it a six or seven out of ten.

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

The pricing depends on the budget allocated to the client; for some, it can be high, and for some not high. But mostly, when the prices are moderate, they are not very high. I would rate it a seven out of ten.

What other advice do I have?

It's a highly scalable, highly robust, and very user-friendly solution. It is easy to set up; the most important point is that it is on a cloud. The solution is also very easy to deploy. Only some connectivity features need to be developed.

I give it an eight 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: My company has a business relationship with this vendor other than being a customer. partner
PeerSpot user
Associate Principal - Cloud Solutions at Apexon
Real User
Dec 12, 2022
Provides a holistic solution when it comes to security, monitoring and access control, making it a go-to database
Pros and Cons
  • "Cosmos DB makes life easier because if we want to use Mongo-type data, or Cassandra-type data, or maybe even just a simple cable storage-type data, then graph, there are multiple ways to do this."
  • "I would like to see Cosmos DB introduce a feature that would convert machine language to human-readable queries."

What is our primary use case?

At the end of the day, Cosmos DB is a database. It is a wrapper over different APIs.

We use Cosmos DB both internally and with our customers. Our internal use is quite extensive. The usage with our customers depends on whether it is an approved technology within their ecosystem.

Because Cosmos DB uses multiple APIs, it is the go-to database for us internally.

What is most valuable?

Cosmos DB makes life easier because if we want to use Mongo-type data, or Cassandra-type data, or maybe even just a simple cable storage-type data, then graph, there are multiple ways to do this. With Cosmos DB, we can put together a holistic solution when it comes to Azure security policies, Azure Monitor, and access control.

What needs improvement?

By design, Microsoft Azure Cosmos DB provides multiple APIs. You have to decide where to write to. Will you write to Excel, Word, PPT, or OneNote? You have to do the homework properly. If there is no tool, then there will be no provision, then there is no database.

I would like to see Cosmos DB introduce a feature that would convert machine language to human-readable queries. For example, if we want to generate a simple diagram that shows the relationship between devices and how frequently have they failed at various locations, we have to consider that the IoT data that is put into Cosmos DB, called byte codes, is not readable to humans. This is a machine language type of data. So when we push that type of data it looks like gibberish, because it is not meant for us, meaning we can't write a normal query. We have been asking for years for them to work with the IoT partner to provide a feature to convert the machine language to readable human queries.

For how long have I used the solution?

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

What do I think about the stability of the solution?

The solution is stable. I would give it a five out of five for reliability.

What do I think about the scalability of the solution?

The architectural decisions will tell you how the scaling will happen. 

Scalability is based on the requirements that are set. Configuration decisions can be implemented pretty fast, so the solution scales well. We are predominantly in the US and India, so it is easy to decide which geographies we need to have and which data we need to synchronize. 

For some of our customers, there are data residency rules like the UAE for example, where patient data must stay within the UAE, making it only one geography. When this is the case, we go for multiple replicas. 

Internally, we have more than 150 developers who use Cosmos DB. Overall, the scalability of the solution is a five out of five.

How are customer service and support?

Product support is pretty good. They have a very good roadmap and the team provides regular patches and regular service updates, and they have a very good release plan.

Microsoft's technical support is good, I rate it a five out of five.

How would you rate customer service and support?

Positive

How was the initial setup?

The initial setup depends on the type of setup you require. You have to design it properly. The architects need to do some homework to ensure the purpose and the requirements are clear. There are many design decisions that must be made first. Once those decisions are made, the initial setup is quite easy. 

Deployment of the solution was completed within a week.

Overall, I would give the solution a four out of five for ease of setup.

What about the implementation team?

The deployment of Cosmos DB was completed internally, we managed it ourselves.

What was our ROI?

The cost is intricate, the calculator is complex because the cloud is all about counting every penny. It may look like small numbers, $0.001 per GB per day, but when we are talking of terabytes of data per day and the numbers will stack up. One month, we had over 500 terabytes. That's why you need a database expert to design it carefully and spend ample time number crunching. If done properly, the ROI will be good.

I would rate Cosmos DB a four out of five in terms of ROI.

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

Cosmos DB is expensive compared to any virtual machine based on conventional RDBMS like MySQL or PostgreSQL. The reason it is expensive is that it is scalable, reliable and there is no latency. So while Cosmos DB is considered expensive, what a lot of people miss is that the cost includes reliability, scalability, and responsiveness.

Cost also depends on the number of databases, number of replica locations, synchronization, number of queries per minute, and storage. Every client will have a different usage pattern. 

Overall, I would rate Cosmos DB a three out of five in terms of affordability. It is easy to over-provision, and it is easy to under-provision the solution.

Which other solutions did I evaluate?

Prior to choosing Microsoft Azure Cosmos DB, we did try other tools extensively. Because we have servers, we tried MongoDB, SQL Server, MySQL, and PostgreSQL. We settled on Cosmos DB internally because we didn't want to go for machines and trojaning. We wanted to adopt a platform as a service.  

Cost also ended up being a driving factor.

What other advice do I have?

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

Disclosure: My company has a business relationship with this vendor other than being a customer. Gold Partners
PeerSpot user
Buyer's Guide
Download our free Microsoft Azure Cosmos DB Report and get advice and tips from experienced pros sharing their opinions.
Updated: October 2026
Buyer's Guide
Download our free Microsoft Azure Cosmos DB Report and get advice and tips from experienced pros sharing their opinions.