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

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
6th
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 February 2026, in the Managed NoSQL Databases category, the mindshare of Amazon Timestream is 5.9%, down from 9.9% compared to the previous year. The mindshare of Microsoft Azure Cosmos DB is 16.5%, down from 16.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Managed NoSQL Databases Market Share Distribution
ProductMarket Share (%)
Microsoft Azure Cosmos DB16.5%
Amazon Timestream5.9%
Other77.6%
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

"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."
"If you drop a message, the solution's technical support will definitely reply."
"Using Amazon Timestream has been seamless due to its integration within the AWS ecosystem and ease of use for the engineering team."
"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."
"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."
"Change feed is a pretty amazing feature. Once you make the changes, they are quickly read for you, and then you also have geo-replication. You can do a lot of things in your region, and the same regions can be replicated all over the world."
"Our customer is very satisfied with it."
"The graphical representation of data is the most valuable feature of the solution."
"In Microsoft Azure Cosmos DB, one valuable feature is its ability to store data in multiple regions. If one region fails, it automatically switches to a healthy region, ensuring minimal latency and disaster recovery without impacting data latency in applications."
"The speed is impressive, and integrating our power-up database with Kafka was an improvement."
"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."
"We primarily use Cosmos DB because it's a managed platform service, eliminating concerns about hosting and reliability."
 

Cons

"There are disadvantages when it comes to time series databases since you can't delete anything from Amazon Timestream data."
"Arranging the database schema is a bit challenging."
"The tool could be improved by increasing the batch size from one hundred records to five hundred or a thousand to speed up indexing."
"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."
"There are certain features that we would like to see added and we are collaborating with the product teams on these areas."
"What is missing in Microsoft Azure Cosmos DB is definitely cold storage. We know it's coming, but that's currently what is missing—the possibility to park older data in a cold tier."
"The price can always be lower, but currently, it's not a problem."
"I had a challenging experience implementing the emulator with a Mac. I had to install the emulator in a Docker container because it is not natively compatible. A significant amount of time was spent researching how to enable HTTPS communication when connecting the container and the emulator."
"The integration of the on-premise solution with the cloud can be difficult sometimes."
"The customer service is lacking. We have a premier support agreement, but support is hit and miss."
"One area for improvement is the ease of writing SQL queries and stored procedures in Microsoft Azure Cosmos DB."
"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."
"We had some performance issues with a data segregation query. We worked closely with Microsoft to solve the problem of performance where, for example, one query had a delay of almost two or three minutes for this one use case. Microsoft tried to improve the product, but in the end, the solution was to change to MongoDB. MongoDB had better performance."
 

Pricing and Cost Advice

"For 1GB of data, the solution charges $ 0.01 in the US region."
"Amazon Timestream's pricing seems manageable to me."
"We don't see high costs with Amazon Timestream, which may vary by company."
"We pay over $10 million a year to Amazon."
"Microsoft provides fair pricing."
"The RU's use case determines our license fees."
"Cosmos DB's pricing structure has significantly improved in recent months, both in terms of its pricing model and how charges are calculated."
"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."
"There is a licensing fee."
"Azure is a pay as you go subscription."
"Cosmos DB is expensive compared to any virtual machine based on conventional RDBMS like MySQL or PostgreSQL."
report
Use our free recommendation engine to learn which Managed NoSQL Databases solutions are best for your needs.
881,665 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
13%
Manufacturing Company
11%
Financial Services Firm
7%
Outsourcing Company
7%
Legal Firm
12%
Financial Services Firm
11%
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 Enterprise21
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 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?
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...
 

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: December 2025.
881,665 professionals have used our research since 2012.