TimescaleDB vs. Amazon Timestream
blog.timescale.com
TimescaleDB vs. Amazon Timestream
1–10 of 203 posts
Re: TimescaleDB vs. Amazon Timestream
#2That is an interesting test I wanted to see for some time. When Timestream came out I was a bit surprised by its price. It might work well for Enterprise POC but for larger use the cost benefit is not appealing.
Re: TimescaleDB vs. Amazon Timestream
#3Did not expect these results, has anyone done similar tests with other timeseries databases?
Re: TimescaleDB vs. Amazon Timestream
#4Did not expect these results, has anyone done similar tests with other timeseries databases?
The blog post links to a comparison done by the CrateDB folks (https://crate.io/a/amazon-timestream-first-impressions/)
Re: TimescaleDB vs. Amazon Timestream
#5Not a surprising result at all. Timestream is another case of AMS trying to make something for the sake of having it (see here Kinesis instead of just doing Kafka and many other products) instead of just adopting something industry standard. That isn't to say they don't do some good stuff just they also ship a lot of crap, very much 2 tiers of products in the AWS catalog.
I would eventually like to see comparison for a more analysis heavy workload vs Druid though.
Simple metrics workloads like what Timestream and Influx do aren't really of interest when comparing to Timescale ability to do JOINs and use other SQL and PostgreSQL specific functionality.
Re: TimescaleDB vs. Amazon Timestream
#6Timescale is what you want to go with in case of RDMSes with audibility in terms of change management over time.
It is the THING.
Thanks the timescale team for making this happening!
Re: TimescaleDB vs. Amazon Timestream
#7Not a surprising result at all. Timestream is another case of AMS trying to make something for the sake of having it (see here Kinesis instead of just doing Kafka and many other products) instead of just adopting something industry standard. That isn't to say they don't do some good stuff just they also ship a lot of crap, very much 2 tiers of products in the AWS catalog. I would eventually like to see comparison for…
It seems like AWS is just focusing on increasing it's vendor lock in and it makes sense not just from the AWS point of view but if you're a developer at an enterprise company that has authorised AWS the more databases the clone, poorly or badly the more choice you have without having to get authorisation and the cost doesn't matter to the developer since the enterprise company is paying for it.
I suspect there are many enterprises that are already so locked into AWS that it would take them a decade to move to a different provider.
Re: TimescaleDB vs. Amazon Timestream
#8Not a surprising result at all. Timestream is another case of AMS trying to make something for the sake of having it (see here Kinesis instead of just doing Kafka and many other products) instead of just adopting something industry standard. That isn't to say they don't do some good stuff just they also ship a lot of crap, very much 2 tiers of products in the AWS catalog. I would eventually like to see comparison for…
It seems like AWS is just focusing on increasing it's vendor lock in and it makes sense not just from the AWS point of view but if you're a developer at an enterprise company that has authorised AWS the more databases the clone, poorly or badly the more choice you have without having to get authorisation and the cost doesn't matter to the developer since the enterprise company is paying for it. I suspect there are ma…
I don't have much expertise with Timestream. Can't comment on it. But, there is nothing wrong in trying for an alternate implementation. We're using Kinesis and it is a good fit in our stack with lot less overhead. They did bring Kakfa (Amazon MSK) later to the AWS service list. Its upto the consumer to pick Kinesis or MSK.
One example which was influential in nature - Dyanmodb. The Dyanmodb paper inspired a number of NoSQL databases, including Apache Cassandra. If they have went with the popular NoSQL database at that time, we might have missed some good contribution.
Re: TimescaleDB vs. Amazon Timestream
#9Not a surprising result at all. Timestream is another case of AMS trying to make something for the sake of having it (see here Kinesis instead of just doing Kafka and many other products) instead of just adopting something industry standard. That isn't to say they don't do some good stuff just they also ship a lot of crap, very much 2 tiers of products in the AWS catalog. I would eventually like to see comparison for…
I remember the announcement of Sagemaker at an AWS summit, a moment of profound embarrassment - the whole thing was barely a Jupyter notebook glued to some EC2 stuff with duct tape.
You're right, they're definitely doing things for the sole purpose of locking you in.
Re: TimescaleDB vs. Amazon Timestream
#10Not a surprising result at all. Timestream is another case of AMS trying to make something for the sake of having it (see here Kinesis instead of just doing Kafka and many other products) instead of just adopting something industry standard. That isn't to say they don't do some good stuff just they also ship a lot of crap, very much 2 tiers of products in the AWS catalog. I would eventually like to see comparison for…
In my opinion it would be very hard to justify using Timestream for any analysis heavy workloads for at least three reasons:
1. Queries will need to touch a lot of data - will cost a lot, and there is no ability to optimize the queries in any way (no EXPLAIN, no indexes, no downsampling)
2. No integration with data exploration and visualization tools
3. No ability to have non-timeseries data, or correlate any data in two different tables (no JOINs)
(Disclaimer: I work at TimescaleDB)