Try our new research platform with insights from 80,000+ expert users
reviewer2596239 - PeerSpot reviewer
Hands on user at a manufacturing company with 10,001+ employees
Real User
Top 20
Switching to the cloud significantly improved scalability, flexibility, and uptime
Pros and Cons
  • "The connectors, such as the MongoDB connector and the integration with SQL, are incredibly valuable."
  • "Switching to the cloud significantly improved scalability, flexibility, and uptime."
  • "There's a little bit of a learning curve because I was new to Azure. But once you learn the tool, it's pretty straightforward."

What is our primary use case?

Our primary use case for Cosmos DB is unstructured data. We utilize it to spin up databases quickly.

How has it helped my organization?

We previously used on-premises databases. Switching to the cloud significantly improved scalability, flexibility, and uptime. It also addressed our uptime issues and greatly benefited our organization. We've never had issues searching through any amount of data; it's more than capable of searching large amounts of data. 

What is most valuable?

The connectors, such as the MongoDB connector and the integration with SQL, are incredibly valuable.

What needs improvement?

There's a little bit of a learning curve because I was new to Azure. But once you learn the tool, it's pretty straightforward.

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

For how long have I used the solution?

I have been using the solution for about three years now.

What do I think about the stability of the solution?

We haven't noticed any significant issues with latency, but we don't have many applications. The availability is excellent, and we have multiple availability zones, so nothing goes down. 

What do I think about the scalability of the solution?

The solution can scale very well both up and down, although we predominantly work with smaller databases. We haven't needed extensive scalability yet, but it seems very capable.

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

We previously used MongoDB. The shift to Cosmos made sense as we wanted to move to the cloud and benefit from its MongoDB API connection.

How was the initial setup?

The setup was straightforward. Team members could start using the tool within a few hours, although not at an expert level.

What was our ROI?

As far as I know, it's cheaper compared to running on-prem, although comparing costs exactly can be challenging.

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

I personally don't deal much with budgets, but our financial analyst hasn't raised any complaints. The pricing aligns well with budget expectations.

What other advice do I have?

I would rate the product an eight or nine out of ten. We are very happy with it as it runs smoothly right out of the box.

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
PeerSpot user
Maria Pallante - PeerSpot reviewer
EVP, Technology Solutions at Bond Brand Loyalty
Real User
Top 20
Provides excellent search result quality but it requires full DR replication
Pros and Cons
  • "The most valuable aspect of Cosmos DB is its performance."
  • "We'd like to avoid full DR replication if possible, as this would result in significant cost savings."

What is our primary use case?

We use Microsoft Azure Cosmos DB in our loyalty platform, which is based on our proprietary technology, Synapse LX. In loyalty, we need to enroll, score, and deliver rewards communications in near real-time. There are significant volume spikes in those activities, so our use case is to support the writing of information into our database. Cosmos DB is a no-SQL database that allows us to scale quickly and handle large volume spikes. It allows us to auto or manually scale in many different ways. It gives us much flexibility to handle that requirement and ensure we deliver the right customer experiences.

How has it helped my organization?

Cosmos DB is not difficult to use, but like anything, it requires careful planning and consideration of use cases. This is especially important when planning to implement it. From an optimization perspective, Microsoft has made significant efforts in the past 12 to 18 months to facilitate changes after initial implementation and optimize cost.

Cosmos DB provides excellent search result quality. Since implementing it, we have not encountered any issues with our searches.

After deploying Cosmos DB, we initially experienced some performance gains, followed by additional benefits that required a learning curve regarding tuning and configuration. As our understanding deepened, we were able to optimize it further.

In the last three months, Cosmos DB has helped reduce our total cost of ownership. Microsoft recently implemented a feature that allows us to achieve savings of up to 50 percent.

What is most valuable?

The most valuable aspect of Cosmos DB is its performance. It serves as the foundation for OpenAI's infrastructure, providing us with similar functionality. This not only prepares us for AI use cases but also efficiently supports our loyalty use cases. We can share information with our customers and deliver experiences without concern about performance.

What needs improvement?

For our Disaster Recovery plan, we currently use geo-replication. We'd like to avoid full DR replication if possible, as this would result in significant cost savings.

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?

We have not had any stability issues with Cosmos DB.

What do I think about the scalability of the solution?

Cosmos DB's scalability is excellent, which is the whole reason to use it for scalability and performance.

The dynamic scaling helps decrease our overhead costs.

How was the initial setup?

The initial deployment was straightforward and consisted of two to three people.

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

Cosmos DB's pricing structure has significantly improved in recent months, both in terms of its pricing model and how charges are calculated. This has led to substantial cost savings for both us and our customers.

What other advice do I have?

I rate Microsoft Azure Cosmos DB seven out of ten because of the disaster recovery requirements.

Cosmos DB presents a steep learning curve. I would rate it a five out of ten. The challenge lies not so much in understanding its concepts as in utilizing them effectively and efficiently.

It took us 12 to 18 months of focused attention to fully onboard our team. At that point, we began to understand. However, it wasn't until we went live and observed actual user activity that we truly grasped the whole picture. Testing is one thing, but experiencing real-world interactions provides invaluable insights and a deeper understanding.

Cosmos DB requires minimal maintenance, but monitoring its performance and optimizing it as needed is crucial.

Potential users should plan accordingly, as Cosmos DB is a NoSQL database that uses similar design principles. Consider the design and apply those principles beforehand to optimize performance from the start. Understanding your read-and-write ratio is crucial due to cost implications, so ensure you understand the balance between reading and writing to the database. All these factors matter as they can impact your costs, so consider them carefully. 

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
Flag as inappropriate
PeerSpot user
Buyer's Guide
Microsoft Azure Cosmos DB
April 2025
Learn what your peers think about Microsoft Azure Cosmos DB. Get advice and tips from experienced pros sharing their opinions. Updated: April 2025.
849,190 professionals have used our research since 2012.
reviewer2595849 - PeerSpot reviewer
Partner Solution Architect (Microsoft Power Platform) at a tech vendor with 1,001-5,000 employees
Real User
Top 20
Seamless record creation with JSON for efficient data handling
Pros and Cons
  • "I like the way you can create and delete records. You pass a JSON, and then it creates a record."
  • "It is easy to use because you don't need to know much about Cosmos DB or have prior experience."
  • "Once you create a database, it calls the container, and then items show up. A better description and more guidance would help because the first time I created it, I didn't understand that a container is similar to a table in SQL."
  • "A better description and more guidance would help because the first time I created it, I didn't understand that a container is similar to a table in SQL."

What is our primary use case?

I am building an extension app for DocuSign. One of the ways for me to demonstrate this is by using a third-party database. I read and write data from Cosmos DB using DocuSign tools.

How has it helped my organization?

We wanted to use Azure function apps and Cosmos DB because Cosmos is serverless and non-relational, so it's easy to set up and simple to scale up and down. Overall, it was a good fit. 

What is most valuable?

I like the way you can create and delete records. You pass a JSON, and then it creates a record. It is easy to use because you don't need to know much about Cosmos DB or have prior experience. 

Cosmos DB does a pretty good job of searching. I've never had trouble as long as I search for a unique key or value I'm looking for. If my query is right, it returns the value.

What needs improvement?

Once you create a database, it calls the container, and then items show up. A better description and more guidance would help because the first time I created it, I didn't understand that a container is similar to a table in SQL. 

For how long have I used the solution?

I have been using it for six months.

What do I think about the scalability of the solution?

My use case is like a proof of concept, so the data set is not extremely large, but I know from reading about it that it can scale up well. It should do a good job on large amounts of data. 

How was the initial setup?

The initial setup was simple the first time I used Cosmos DB. It took just a few hours for my small technical team to get used to how Cosmos DB works.

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

The pricing model has aligned with our expectations. In Azure, setting it as consumption-based or serverless keeps the cost low, but we had instances where automation increased the cost significantly. It was more of a configuration problem, where options to keep it minimal are still present.

Which other solutions did I evaluate?

We wanted to go with Azure function apps and Cosmos DB to keep it serverless and non-relational, making it easy to set up, scale up, and down.

What other advice do I have?

I rate the product as 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: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Brandon Smith - PeerSpot reviewer
Senior Software Developer at United Airlines
Real User
Removes bottlenecks related to databases in our application and works quickly because of reference keys
Pros and Cons
  • "The biggest benefit it offers is scalability. It's easier to work with concurrency and updating data."
  • "An improvement would be a more robust functionality around updating elements on a document, or some type of procedural updates that don't require pulling the entire document."

What is our primary use case?

We use Cosmos DB as our entire storage database solution for our application. We don't use any other relational database. We have a file that we use for configuration, but we use Cosmos for user data.

We have about 100,000 users a week who visit our website. We have plans to increase usage to four times what we're using now.

How has it helped my organization?

The biggest benefit it offers is scalability. It's easier to work with concurrency and updating data. We don't have to worry about locking cables or the speed of reads or query searches because we've structured our data around a key value. Everything is super fast, and it basically removes any bottleneck related to databases in our application, and we just use reference keys. One document will reference the key of another document that we need, so we don't have to rely on searching.

What is most valuable?

Partitioning is helpful because we use it heavily. Partitions are really nice because they help with the collection of data. Not only is it fast to recall the data, but when you partition it, you can pull the partition and then query the exact document from that partition. It helps with data recall.

What needs improvement?

There's another feature that we just started implementing, which is partial updates of documents. It doesn't require the entire object to update, but updating documents across applications becomes difficult because you have to pull the entire document, which means you have to support the entire model to update it. So, that application has to know about every single parameter that may or may not have been added because if it reads and writes the document again, you'll lose data elements.

An improvement would be a more robust functionality around updating elements on a document, or some type of procedural updates that don't require pulling the entire document. Otherwise, you have to keep all of your apps up to date with the models, and that can be cumbersome and lead to errors. Usually, you don't always remember, and then it leads to some type of bug, but you won't realize why. You'll lose some value because you don't realize that you have some application that doesn't run often. You forget that it writes to that same document and you didn't update the model.

It would be nice to have some type of functionality for less common updating applications and to not always have to worry about keeping that model up to date.

There's some integration with Entity Framework and it's nice, but it's not robust and it would be good to have something like that when it comes to pulling data.

Occasionally, you have to query the database for values because we save our appointments and we don't have an index on appointments. We don't have a manual lookup for appointments, so we don't save it in another file. We have to run a query to get appointments that occur on a specific day and the downside of that is you have to use strings just to hardcode the string values. It would be nice to more easily integrate with a tool like Entity Framework, and I know that they do, but it's not an easy process. It would be nice to have an easier way without relying on text to query the database.

For how long have I used the solution?

I have used Cosmos DB for a year and a half.

What do I think about the stability of the solution?

There have been some configuration issues, but we haven't hit any thresholds or roadblocks when it comes to throughput. That was one of the reasons that we leaned toward it and not a relational database, especially at scale. We haven't run into any issues when it comes to that.

How are customer service and support?

We look at community answers because we can usually get answers faster than messaging support directly. We don't usually resort to a customer service type of support unless it's a fundamental issue. 

When we had an outage in the middle of the night, the turnaround time was within a few hours.

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

Previously, I used Couchbase. I've also used Neptune, which is a different type of database. I've also used SQL.

We chose Cosmo DB because it's more tightly integrated. One of the reasons we chose this version of a non-relational database was because of the speed of development. We also chose Cosmos DB over other types of NoSQL databases because it's so tightly integrated with Azure, it's easily managed through deployment templates, and it's very easy to scale. If you're using Azure already, it's a very easy tool to pick up and integrate into your applications.

How was the initial setup?

Cosmos is pretty straightforward. There is more complexity, so you just have to be mindful. We had a small issue with making sure that the disaster recovery settings were set up correctly. We found out that there was some type of outage in the middle of the night, but we noticed that the failover didn't run properly. It was because of some configuration that should have been caught earlier, and it wasn't obvious that we got it wrong.

There are some infrastructure teams that manage some underlying resources that are related to Cosmos and some of the configurations, but for our specific implementation, we have three developers at most. We usually only need two people for maintaining and managing the solution.

What about the implementation team?

We deployed the solution in the cloud, but we configured everything in-house.

What was our ROI?

We have seen ROI. There's no active management when it comes to that. When I've worked on relational databases, there's a lot that goes on, like indexing, upgrades, and store procedures. I've managed relational databases for years while working on an application and worked with people who managed them. Cosmos is nearly maintenance-free and very easy to use.

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

The pricing is really good. I would rate the cost as 9 out of 10. There may be some more complicated use cases that are more expensive. When we've budgeted for our resources, it's one of the more expensive ones, but it's still not very expensive per month.

What other advice do I have?

I would rate this solution as 8 out of 10. 

When it comes to ease of use, spinning up and working at scale, our specific use case, and the scalability that it offers, the solution is definitely very good.

My advice is to use containers as single objects and create manual indexing to improve efficiency.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Lead Data Engineer at ASOS.com Limited
Real User
Top 20
Requires minimal maintenance and is relatively easy to use with a small learning curve.
Pros and Cons
  • "The autoscale feature is the most useful for us."
  • "While Microsoft Azure Cosmos DB is generally easy to use, it has some limitations."

What is our primary use case?

In my role, I use Microsoft Azure Cosmos DB fairly extensively across various platforms. At ASOS, we utilize it for order processing to record incoming orders and for commercial integration platforms. Overall, we have numerous use cases.

How has it helped my organization?

Overall, Microsoft Azure Cosmos DB is easy to use.

Microsoft Azure Cosmos DB has provided benefits compared to SQL databases, particularly in terms of availability.

Microsoft Azure Cosmos DB has helped to improve our total cost of ownership.

Microsoft Azure Cosmos DB offers a relatively easy learning curve due to its limited programming service area compared to SQL Server. This streamlined functionality allows users to quickly grasp the SQL query language.

What is most valuable?

The autoscale feature is the most useful for us.

What needs improvement?

There should be parity between the various APIs. I often work with the Mongo API, and features for it sometimes lag substantially behind the core API, such as the Analytical Store feature. Additionally, I am waiting for the full fidelity change feed that would surface all changes, including deletes to documents.

While Microsoft Azure Cosmos DB is generally easy to use, it has some limitations. Certain areas are more restrictive, and we are awaiting features that will simplify development. For example, currently under development, the full fidelity change feed will expose all document changes, enabling tasks like synchronizing collections while accounting for deletions. This is challenging because the existing change feed doesn't provide information about deleted documents.

For how long have I used the solution?

I have been using Microsoft Azure Cosmos DB for around seven years.

What do I think about the stability of the solution?

Cosmos DB demonstrates good stability and great reliability, with technical issues arising approximately once per year.

While Cosmos DB offers good latency and availability, careful consideration must be given to selecting appropriate consistency levels.

What do I think about the scalability of the solution?

The scalability is excellent, and as long as the data can be partitioned, the scalability is nearly infinite.

Cosmos DB's ability to scale workloads is a significant advantage, as evidenced by our successful management of multiple terabytes of data without encountering any issues.

How are customer service and support?

The quality of customer service and support varies. We always get an answer eventually, but the speed of resolution depends on the reason for the support ticket. If there is a bug in the product, we have to wait for it to be fixed.

How would you rate customer service and support?

Positive

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


How was the initial setup?

The initial setup of Microsoft Azure Cosmos DB is straightforward. Even someone with no experience can easily deploy the solution.

The deployment can be completed by one person on the same day.

What about the implementation team?

The deployment can be done entirely in-house. Whether we are doing it manually in the portal or deploying it through Terraform, it is straightforward. We do not require help from an integrator or consultant, although there are considerations about partitioning collections when creating resources.

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

The pricing for Cosmos DB has improved, particularly with the new pricing for Autoscale. Previously, we were charged according to the busiest partition across all regions, but now, each partition is only charged for what it uses. This change has substantially reduced our costs.

Which other solutions did I evaluate?

When evaluating new projects, we determine whether data storage is best suited for a relational database, such as Azure SQL Database, or a non-relational database like Cosmos DB.

What other advice do I have?

I would rate Microsoft Azure Cosmos DB eight out of ten.

Understanding some of the subtleties of Microsoft Azure Cosmos DB can take time, and some individuals at ASOS still find concepts like partitioning unclear. However, getting started with Cosmos DB and developing functional applications is quick and can be achieved in a short timeframe.

We require minimal maintenance to validate that we've configured, for example, the correct indexing policies as required by our queries.

New users should make sure they understand partitioning because once it's selected, it is difficult to change it. Otherwise, you would need to migrate everything over to another collection.

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: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Flag as inappropriate
PeerSpot user
MatthewSpieth - PeerSpot reviewer
Senior Data Engineer Consultant at a computer software company with 201-500 employees
Consultant
Top 10
Schema-free nature, offers good speed and doesn't rely on traditional disks and database structures like a relational database
Pros and Cons
  • "The initial setup is simple and straightforward. You can set up a Cosmos DB in a day, even configuring things like availability zones around the world."
  • "It's still new, and good training resources are harder to find. Even the most recent books on Cosmos DB are several years old, which is ancient in IT terms."

What is our primary use case?

I like to describe it as a programmer's database. .NET developers, in particular, can design and work with the data easily because it's schema-free. Unlike traditional databases, which are considered rigid with their rules, developers really love Cosmos DB because of its schema-free nature and the freedom it offers.

Cosmos is widely used for web applications. You can also use it for inventory management and IoT solutions... there are a ton of different applications.

How has it helped my organization?

It's very easy to integrate Azure Cosmos DB with other Azure services. For example, generating a Power BI report from data in Cosmos is just a few clicks. It's also simple to stream IoT or sensor data into Cosmos.

What is most valuable?

When it comes to supporting IoT or real-time analytics, the main advantage is speed. Cosmos DB doesn't rely on traditional disks and database structures like a relational database. It uses JSON, which is similar to XML, and that makes it incredibly fast.

The way it was designed is most valuable for global distribution. Unlike old-school SQL Server that was intended for a single data center, Cosmos was built from the ground up for global availability. 

Features like geo-clustering and mirroring were not afterthoughts. If you have a database in Chicago, you can right-click and easily create a failover group in Japan. That works well for global companies with offices across continents; it minimizes latency.

Cosmos's multi-model support made databases more highly available. 

What needs improvement?

The downside is that Cosmos is new and fairly complex. There's a limited pool of talent who are really good at working with it.

Because of that, I've been approached by recruiters quite a bit; they see my Cosmos DB certification on LinkedIn. It's hard to find people to work on Cosmos projects. 

Sometimes, a really smart developer will design and build a Cosmos implementation and then move on, leaving the company struggling to find someone to work with it and maintain it.

Interestingly, if you need to restore a Cosmos DB database, you have to put in a ticket with Microsoft – they're the only ones who can do that.

For how long have I used the solution?

I've worked with Cosmos on and off for about three years.

How are customer service and support?

For Cosmos DB, their technical support is very good. They are the experts in that product.

Overall, the customer service and support are excellent. 

How would you rate customer service and support?

Positive

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

I did a couple days of training on DynamoDB, which is Amazon's comparable product to Cosmos DB.

They're actually quite similar, both being multi-model databases. Relational databases are good for structured data, but once you get into semi-structured and unstructured data, they just don't perform well. 

That's where DynamoDB and Cosmos DB excel – storing, indexing, and quickly working with that less-structured data.

How was the initial setup?

The initial setup is simple and straightforward. You can set up a Cosmos DB in a day, even configuring things like availability zones around the world. 

The harder part is on the developer side – designing the collections (similar to tables) and how the data will flow in.

What about the implementation team?

I've set up a few Cosmos DB instances, and it's about a half-hour tops.

One person can handle the deployment. I'd typically set it up alongside other Azure components like a VM. You choose your settings, networking details, etc., basically walk through a wizard, hit deploy, and it's up within half an hour.

There are some configuration options for database administration on the customer's side. You'll need to go in and enable things like automatic indexing with checkboxes.

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

With heavy use, like a large-scale IoT implementation, you could easily hit a quarter of a million dollars a month in Azure charges if Cosmos DB is a big part of it.

What other advice do I have?

I would recommend using it, but with a caveat – it's a good fit for companies with deep pockets.

It's powerful and amazing, but the costs can add up.

I'd give it an eight out of ten. It's super powerful and solves real problems with global distribution. I hesitate to give it a perfect ten because it's still new, and good training resources are harder to find. Even the most recent books on Cosmos DB are several years old, which is ancient in IT terms.

I had to work hard to get a certification in it. 

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Venkat Narra - PeerSpot reviewer
Senior Technical Director at Atlas Systems
Real User
Top 20
The solution has helped improve search result quality and it effectively searches large amounts of data
Pros and Cons
  • "The speed is impressive, and integrating our power-up database with Kafka was an improvement."
  • "The speed is impressive, and integrating our power-up database with Kafka was an improvement."
  • "One area of improvement for Cosmos database is the auto-scaling of RUs during high loads. It would be beneficial if the database could automatically scale resources rather than requiring manual adjustments."

What is our primary use case?

We use Cosmos DB to store the concept of data and how it is entered by the user.

How has it helped my organization?

Cosmos database has helped improve search result quality, allowing more results. We implemented the ASR service to gather data from users. Cosmos database does an excellent job of searching through large amounts of data. The speed is impressive, and integrating our power-up database with Kafka was an improvement.

What is most valuable?

The most valuable features of the Cosmos DB include its ease of use and optimization and its seamless integration with code. We do not use the built-in vector database capability, but its interoperability with Azure AI services is noteworthy.

What needs improvement?

One area of improvement for Cosmos database is the auto-scaling of RUs during high loads. It would be beneficial if the database could automatically scale resources rather than requiring manual adjustments.

For how long have I used the solution?

I have been using Cosmos DB for two years.

What do I think about the scalability of the solution?

To scale workloads effectively with Cosmos database, we must manually increase the RUs. During the initial implementation phases, we encountered issues with scaling, but it appears to have been resolved.

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

We replaced our SQL database with Cosmos and Kafka, resulting in an improvement in operational performance.

How was the initial setup?

The initial setup was straightforward and did not take much time.

What other advice do I have?

I rate Azure Cosmos DB eight out of 10. The system itself is effective for our current use cases.

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: Gold Partner
Flag as inappropriate
PeerSpot user
Aditya Bhalla - PeerSpot reviewer
Software Development Engineer IV at InMobi
Real User
Top 10
Geo-replication and scalability help us in managing workloads efficiently
Pros and Cons
  • "The most valuable features of Microsoft Azure Cosmos DB include the TTL, the ability to scale up and down as needed, and geo-replication, which comes out of the box."
  • "Microsoft Azure Cosmos DB can be improved by providing more fine-grained control over certain aspects, such as connections and threads. There could be more control over how many connections are made."

What is our primary use case?

The main use case for Microsoft Azure Cosmos DB is as a key-value store where we store all the user data that we have and perform lookups. We use it at a significant scale, with storage of unique data reaching 12 terabytes and handling up to 3 million requests per second.

How has it helped my organization?

The scalability of Microsoft Azure Cosmos DB has significantly aided us in managing workloads efficiently.

We were able to realize the benefits of Microsoft Azure Cosmos DB immediately after deployment, making it quite easy to get started.

What is most valuable?

The most valuable features of Microsoft Azure Cosmos DB include the TTL, the ability to scale up and down as needed, and geo-replication, which comes out of the box. We do not have to do anything for geo-replication. We just have to enable it.

The indexing policy is also very good, and the overall metrics and monitoring system are also quite good.

Microsoft Azure Cosmos DB is fairly easy to use.

What needs improvement?

Microsoft Azure Cosmos DB can be improved by providing more fine-grained control over certain aspects, such as connections and threads. There could be more control over how many connections are made. I am not sure if it is a knowledge gap issue. A regular connection with the Azure Cosmos DB team might help in addressing knowledge gaps. Being able to fine-tune these features would be helpful for us.

For how long have I used the solution?

I have been using Microsoft Azure Cosmos DB for about six years.

What do I think about the stability of the solution?

Over the last two years, Microsoft Azure Cosmos DB has been very stable. It has very good latency and availability. Latency is good on the server side and the client side. We have had only one significant issue that affected our production system. Overall, stability has been excellent.

What do I think about the scalability of the solution?

The scalability of Microsoft Azure Cosmos DB is one of its best attributes. We can scale very efficiently and adjust workloads as needed, which is more challenging with other systems.

How are customer service and support?

We have contacted their support many times. The quality of customer and technical support has improved over the years. Initially, it used to take quite a while for issues to be resolved, but now the support is seamless and very efficient. We have not needed much support in the last couple of years due to the system's stability. It is pretty stable now. I would rate their support a nine out of ten.

How would you rate customer service and support?

Positive

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

I have used Redis briefly and Aerospike extensively before switching to Microsoft Azure Cosmos DB.

Both Microsoft Azure Cosmos DB and Aerospike have their own advantages. The biggest advantage of Microsoft Azure Cosmos DB is that it is very easy to get started with and it does not require too much effort. It takes just one click to deploy Microsoft Azure Cosmos DB and put it into multiple regions. It does not require too much maintenance, whereas Aerospike requires a lot of maintenance effort. It requires a dedicated team. In this aspect, Microsoft Azure Cosmos DB is very good. However, Aerospike provides control over a few things, which we do not have in Microsoft Azure Cosmos DB. If we want to run or use the maximum amount of resources, Aerospike helps a lot. Both have their advantages and disadvantages.

How was the initial setup?

The initial setup was easy. It was not difficult.

It took us a quarter to be able to use it efficiently. It is fairly easy and straightforward.

We had set up our own autoscaler. There was a pipeline that ran on top of Azure Cosmos DB to see how many RUs were provisioned. It did require a little bit of maintenance because we built custom software on top of that, but that was it. Our autoscaler performed better than Azure Autoscaler. However, because of some billing benefits, we have started using Azure Autoscaler. The Microsoft team said that if we used Azure Autoscaler, they would give us a discount, so we started using that, but our autoscaler performed better.

What about the implementation team?

Initially, the deployment required an entire team, but now, it can be managed by a smaller team of two to three engineers.

What was our ROI?

It has decreased our total cost of ownership by approximately 20% compared to other alternatives such as Redis.

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

Its pricing is higher compared to solutions like Aerospike. However, it is justified because of the out-of-the-box features that are provided. The availability and resiliency that we have make it worth the price.

What other advice do I have?

To new users, I would advise first knowing their data. They should know whether it fits their solution, which Azure Cosmos API to use, and what scale they intend to run it.

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

Which deployment model are you using for this solution?

Public Cloud
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
PeerSpot user