No more typing reviews! Try our Samantha, our new voice AI agent.

Amazon Timestream vs Microsoft Azure Cosmos DB comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 25, 2026

Review summaries and opinions

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

Categories and Ranking

Amazon Timestream
Ranking in Managed NoSQL Databases
7th
Average Rating
9.0
Reviews Sentiment
6.9
Number of Reviews
5
Ranking in other categories
No ranking in other categories
Microsoft Azure Cosmos DB
Ranking in Managed NoSQL Databases
1st
Average Rating
8.2
Reviews Sentiment
6.9
Number of Reviews
109
Ranking in other categories
Database as a Service (DBaaS) (4th), NoSQL Databases (2nd), Vector Databases (1st)
 

Mindshare comparison

As of May 2026, in the Managed NoSQL Databases category, the mindshare of Amazon Timestream is 5.2%, down from 8.8% compared to the previous year. The mindshare of Microsoft Azure Cosmos DB is 15.7%, down from 16.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Managed NoSQL Databases Mindshare Distribution
ProductMindshare (%)
Microsoft Azure Cosmos DB15.7%
Amazon Timestream5.2%
Other79.1%
Managed NoSQL Databases
 

Featured Reviews

Sushil Pandey - PeerSpot reviewer
Data Engineer at Tiger Analytics
It is helpful to get telemetry data from the devices in real-time
It is an easily scalable solution. When it comes to the retention period, if someone wants to change, they have to define it at the start. Later on, if users want to change it again, like, or increase the retention policy, then they have to create the table again and do so, and if it is not done, then we face problems. It will increase the retention, but when you try to insert a record or an older record that is not included in the range of your retention period, then you can face some problems and, like, it will throw some errors. The tool is scalable, but it should be defined at the start as to how much retention you want. For scalability, I rate the tool a six or seven out of ten.
reviewer2724105 - PeerSpot reviewer
Senior Director of Product Management at a tech vendor with 1,001-5,000 employees
Provides super sharp latency, excellent availability, and the ability to effectively manage costs across different tenants
For integrating Microsoft Azure Cosmos DB with other Azure products or other products, there are a couple of challenges with the current system. Right now, the vectors are stored as floating-point numbers within the NoSQL document, which makes them inefficiently large. This leads to increased storage space requirements, and searching through a vast number of documents in the vector database becomes quite costly in terms of RUs. While the integration works well, the expense associated with it is relatively high. I would really like to see a reduction in costs for their vector search, as it is currently on the expensive side. The areas for improvement in Microsoft Azure Cosmos DB are vector pricing and vector indexing patterns, which are unintuitive and not well described. I would also like to see the parameters of Fleet Spaces made more powerful, as currently, it's somewhat lightweight. I believe they've made those changes intentionally to better understand the cost model. However, we would like to take a more aggressive approach in using it. One of the most frustrating aspects of Microsoft Azure Cosmos DB right now is that you can only store one vector per document. Additionally, you must specify the configuration of that vector when you create an instance of Microsoft Azure Cosmos DB. Once the database is set up, you can't change the vector configuration, which is incredibly limiting for experimentation. You want the ability to try different settings and see how they perform, as there are numerous use cases for storing more than one vector in a document. While interoperability within the vector database is acceptable—for example, I can search for vectors—I still desire a richer set of configuration options.

Quotes from Members

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

Pros

"The best things about Amazon Timestream are it's maintenance-free, customizable, and has no lag issues. It's always real-time."
"You can quickly aggregate data from the last ten years with Amazon Timestream."
"Using Amazon Timestream has been seamless due to its integration within the AWS ecosystem and ease of use for the engineering team."
"If you drop a message, the solution's technical support will definitely reply."
"What I like best is that the tool is easy to collect and store data and is fast and scalable. The fully managed database is easy to understand."
"What I like about Microsoft Azure Cosmos DB is that it's easy to do data ingestion and use the data in different applications. If you talk about business intelligence such as the Power BI tool, it's easy to connect because both are Microsoft products. With Microsoft Azure Cosmos DB, it's easy to connect and do data ingestion."
"The solution is used because we get faster response times with large data sets than with SQL. It's essential for us because we have half a billion rows, and we need to return them quickly."
"The latency and availability of Microsoft Azure Cosmos DB are fantastic."
"The value that it has added to my AI or search workloads is that I think it's optimized that process and made it easier; we have a lot of unstructured data coming from different dissimilar systems and different data sources, so correlating those things together and making sense of it has been very beneficial."
"We have both our SaaS app and the analytical side running without throttling issues."
"It is a NoSQL database."
"We achieved a strong return on investment."
"The best feature is the velocity to make a query."
 

Cons

"There are certain features that we would like to see added and we are collaborating with the product teams on these areas."
"There are disadvantages when it comes to time series databases since you can't delete anything from Amazon Timestream data."
"The solution could be improved by making it easier for new graduates like me to use. Better explanations of queries and how to use them with other AWS services would help."
"The tool could be improved by increasing the batch size from one hundred records to five hundred or a thousand to speed up indexing."
"Arranging the database schema is a bit challenging."
"While Microsoft Azure Cosmos DB is generally easy to use, it has some limitations."
"The current data analytics of Cosmos DB is inefficient for large-scale queries due to its transactional design."
"Cosmos DB is expensive, and the RU-based pricing model is confusing."
"The model with autoscaling for RU is complicated to optimize RU consumption."
"I would like to see Cosmos DB introduce a feature that would convert machine language to human-readable queries."
"The cost is a concern. Microsoft Azure Cosmos DB did not decrease our total cost of ownership. From the standpoint of the old way of doing DBA operations, it did, but our cloud cost increased significantly."
"Currently, I have no suggestions for enhancement or new implementations in Microsoft Azure Cosmos DB. However, the cost can sometimes be high, especially during cross-partition queries with large data amounts."
"The challenge for us is always scale."
 

Pricing and Cost Advice

"We don't see high costs with Amazon Timestream, which may vary by company."
"Amazon Timestream's pricing seems manageable to me."
"We pay over $10 million a year to Amazon."
"For 1GB of data, the solution charges $ 0.01 in the US region."
"If you are a small organization or startup building from scratch without the Microsoft Startup Founder Club support, it could be expensive."
"Cosmos DB is a managed offering, so its cost is understandably higher."
"Microsoft Azure Cosmos DB's licensing costs are monthly."
"Because of the lack of understanding about RUs, the costs become unpredictable. It sometimes goes over the budget."
"Pricing, at times, is not super clear because they use the request unit (RU) model. To manage not just Azure Cosmos DB but what you are receiving for the dollars paid is not easy. It is very abstract. They could do a better job of connecting Azure Cosmos DB with the value or some variation of that."
"Azure Cosmos DB is generally a costly resource compared to other Azure resources. It comes with a high cost. We have reserved one thousand RUs. Free usage is also limited."
"I would rate Cosmos DB's cost at seven out of ten, with ten being the highest."
"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."
report
Use our free recommendation engine to learn which Managed NoSQL Databases solutions are best for your needs.
893,164 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
14%
Financial Services Firm
14%
Manufacturing Company
11%
Outsourcing Company
9%
Financial Services Firm
12%
Legal Firm
12%
Comms Service Provider
9%
Manufacturing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business33
Midsize Enterprise22
Large Enterprise58
 

Questions from the Community

What needs improvement with Amazon Timestream?
We are working on a few open change requests with the engineering teams on AWS's side. There are certain features that we would like to see added and we are collaborating with the product teams on ...
What is your primary use case for Amazon Timestream?
We use Amazon Timestream as a data historian for IT data. It stores all individual measurements of our customers' IoT devices for a certain period of time, allowing them to perform time-series-base...
What is your experience regarding pricing and costs for Microsoft Azure Cosmos DB?
Microsoft Azure Cosmos DB's pricing model has aligned with my budget expectations because I can tune the RU as I need to, which helps a lot. Microsoft Azure Cosmos DB's dynamic auto-scale or server...
What needs improvement with Microsoft Azure Cosmos DB?
I have not utilized Microsoft Azure Cosmos DB multi-model support for handling diverse data types. I'm not in the position to decide if clients will use Microsoft Azure Cosmos DB or any other datab...
What is your primary use case for Microsoft Azure Cosmos DB?
We have a very large team of developers who develop a solution for our customers. In the part where they need some infrastructure on Microsoft Azure, we deploy entire environments of different type...
 

Also Known As

No data available
Microsoft Azure DocumentDB, MS Azure Cosmos DB
 

Overview

 

Sample Customers

Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
TomTom, KPMG Australia, Bosch, ASOS, Mercedes Benz, NBA, Zero Friction, Nederlandse Spoorwegen, Kinectify
Find out what your peers are saying about Amazon Timestream vs. Microsoft Azure Cosmos DB and other solutions. Updated: April 2026.
893,164 professionals have used our research since 2012.