Try our new research platform with insights from 80,000+ expert users

Chroma vs Microsoft Azure Cosmos DB comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Sep 29, 2024
 

Categories and Ranking

Chroma
Ranking in Vector Databases
2nd
Average Rating
8.6
Number of Reviews
2
Ranking in other categories
No ranking in other categories
Microsoft Azure Cosmos DB
Ranking in Vector Databases
5th
Average Rating
8.2
Reviews Sentiment
7.3
Number of Reviews
76
Ranking in other categories
Database as a Service (DBaaS) (6th), NoSQL Databases (3rd), Managed NoSQL Databases (1st)
 

Featured Reviews

Sameer Bhangale - PeerSpot reviewer
Used for RAG (Retrieval-augmented generation) and provides good documentation
If I have to deploy my application in a scalable environment with lots of data and users, I sometimes need to create multiple instances of my database or have a distributed database across different machines. Using Kubernetes, I can quickly increase the horizontal spread of Milvus because it is containerized and readily available. I don't have to do anything by myself. New users can go to Chroma's 'Get Started' page and follow it like a tutorial. Then, they will be ready to use the solution. Chroma has helped us reduce the overall project post production time. Overall, I rate the solution an eight out of ten.
Michael Calvin - PeerSpot reviewer
Easy to integrate, has a shallow learning curve, and scales dynamically
Azure Cosmos DB is quick to adopt with a shallow learning curve. The average user can be operational within hours or days, handling small to medium data volumes. However, optimizing for ultra-high throughput scenarios involves a steeper learning curve, requiring substantial knowledge to master Azure Cosmos DB. Nonetheless, most users can leverage it as their operational data store with minimal effort. Our platform boasts several extensive language model features, particularly around summarization capabilities. We use vector searching in Azure Cosmos DB to facilitate the retrieval of an augmented generation model with our LLM implementation. It's a standard RAG implementation using Azure Cosmos DB. Compared to other options, a key advantage of vector indexing in Azure Cosmos DB is the ability to query documents alongside vectors. This pinpoints the precise information required for RAG in our LLM solution, granting us greater flexibility than vector searching in other Azure services. We integrated the vector database with the Azure OpenAI service for our LLM solution. The Azure AI services were simple to integrate with the vector database. There was a slight learning curve, especially as we were on the private preview of vector searching. This led to some hiccups with our existing database configurations, specifically regarding continuous backup. We couldn't enable continuous backup and vector searching simultaneously. However, this was solely due to our participation in the preview, and I'm confident this issue won't persist in the general availability release. Azure Cosmos DB is fantastic for searching large amounts of data when the data is within a single partition. Over the last two weekends, we ingested over 400 gigabytes of data into our Azure Cosmos DB database and saw no change in querying performance compared to when our database was only 20 gigabytes in size. This is impressive and powerful, but the scope is limited to those partition queries. The first benefit we've seen is increased developer productivity. Azure Cosmos DB is an easy database to work with. Its schema-less nature allows us to iterate quickly on our platform, develop new features, and store the associated data in Azure. Developers find it easy to use, eliminating the need for object-relational mapping tools and other overhead. Geographic replication and the ability to scale geographically is another advantage. This is challenging with other databases, even other NoSQL databases, but Azure Cosmos DB makes it easy. Cost optimization is a major benefit as well. We've been able to run our platform at a fraction of the infrastructure cost our customers incur when integrating with us. This allows us to focus resources on feature development and platform building rather than infrastructure maintenance. Azure Cosmos DB helped reduce the total cost of ownership. We don't need DBAs, system administrators, or typical IT staff to run the infrastructure because we can use Azure Cosmos DB as a platform or a software-as-a-service data storage solution. This makes the total cost of ownership significantly lower than any comparable solution using relational databases or other NoSQL solutions like MongoDB. We enable auto-scaling on all of our Azure Cosmos DB resources, which helps us achieve cost optimizations.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The solution's most valuable feature is its documentation, which allows new users to easily learn, deploy, and use it."
"It's very easy to set up and runs easily."
"I like the way you can create and delete records. You pass a JSON, and then it creates a record."
"The most valuable feature of Microsoft Azure Cosmos DB is its ability to handle concurrency and consistency."
"It provided a platform to sell a service to customers."
"We achieved a strong return on investment."
"Azure Cosmos DB offers numerous data connectors that provide a platform for seamless integration with various platforms and visualization tools such as Power BI. It allows connection via multiple data connectors to integrate data in any desired format."
"The availability and latency of Azure Cosmos DB are excellent."
"The solution is user friendly and Microsoft's technical support is good."
"We love the ability to land data with Cosmos DB easily. Cosmos is native to Azure, so everything works seamlessly with it. You need good data to have good AI, and Cosmos makes it easy to land the data."
 

Cons

"I think Chroma doesn't have a ready-made containerized image available."
"The hybrid algorithm needs improvement."
"Cosmos DB should continue evolving in AI features. We expect Cosmos DB to lead on that. There is potential for improved security features, which is important for data storage, especially for Dell Technologies. We must ensure data security remains the top priority."
"The solution cannot join two databases like Oracle or SQL Server."
"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."
"The main area of improvement is the cost, as the expense is high. Also, when writing processes into Cosmos, sometimes the threshold is met, which can be a problem if developers have not written the code properly, limiting calls to five thousand. These aspects need addressing."
"We would like to see advancements in AI with the ability to benchmark vector search capabilities, ensuring it answers questions accurately. During our initial implementation, we faced challenges with indexing and sorting, which are natively available in other offerings but required specific configurations in Cosmos."
"For streaming platforms, Azure Cosmos DB could improve efficiency in data storage. Indexing can also be better. Enhanced capabilities are necessary to manage increased data amounts more effectively during searches."
"We should have more freedom to tweak it and make our own queries for non-traditional use-cases."
"I would like the speed of transferring data to be improved."
 

Pricing and Cost Advice

"The current version is an open-source."
"Cosmos DB's pricing structure has significantly improved in recent months, both in terms of its pricing model and how charges are calculated."
"The pricing and licensing model was initially difficult to understand, but as soon as I learned what was going on and how it was priced, it was pretty easy."
"The customer had a high budget, but it turned out to be a little bit cheaper than what they expected. I am not sure how much they have spent so far, but they are satisfied with the pricing."
"Microsoft Azure Cosmos DB's licensing costs are monthly."
"Microsoft provides fair pricing."
"It is expensive. The moment you have high availability options and they are mixed with the type of multitenant architecture you use, the pricing is on the higher end."
"Cosmos should be cheaper. We actually intend to stop using it in the near future because the price is too high."
"It is cost-effective. They offer two pricing models. One is the serverless model and the other one is the vCore model that allows provisioning the resources as necessary. For our pilot projects, we can utilize the serverless model, monitor the usage, and adjust resources as needed."
report
Use our free recommendation engine to learn which Vector Databases solutions are best for your needs.
824,053 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
14%
Manufacturing Company
10%
University
9%
Computer Software Company
14%
Comms Service Provider
12%
Financial Services Firm
11%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about Chroma?
The solution's most valuable feature is its documentation, which allows new users to easily learn, deploy, and use it.
What needs improvement with Chroma?
The hybrid algorithm needs improvement.
What is your primary use case for Chroma?
We collect customer's feedback, and then we present it to the clients.
What do you like most about Microsoft Azure Cosmos DB?
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.
What is your experience regarding pricing and costs for Microsoft Azure Cosmos DB?
The solution was a new product, so we didn't have a cost of ownership before. The cost has not surprised us. It's not been an issue. If we were doing multi-master replication globally, the cost wou...
What needs improvement with Microsoft Azure Cosmos DB?
Using it is easy. We are having trouble optimizing it. I'm not a technical person, so I couldn't explain why, but we're not getting the performance we were expecting. I'm sure it's probably an us p...
 

Comparisons

 

Also Known As

No data available
Microsoft Azure DocumentDB, MS Azure Cosmos DB
 

Learn More

Video not available
 

Overview

 

Sample Customers

1. Google 2. Netflix 3. Amazon 4. Facebook 5. Microsoft 6. Apple 7. Twitter 8. Spotify 9. Adobe 10. Uber 11. Airbnb 12. LinkedIn 13. Pinterest 14. Snapchat 15. Dropbox 16. Salesforce 17. IBM 18. Intel 19. Oracle 20. Cisco 21. HP 22. Dell 23. Samsung 24. Sony 25. LG 26. Panasonic 27. Philips 28. Toshiba 29. Nokia 30. Motorola 31. Xiaomi 32. Huawei
TomTom, KPMG Australia, Bosch, ASOS, Mercedes Benz, NBA, Zero Friction, Nederlandse Spoorwegen, Kinectify
Find out what your peers are saying about Chroma vs. Microsoft Azure Cosmos DB and other solutions. Updated: December 2024.
824,053 professionals have used our research since 2012.