Full title includes a summary of benchmark results for the lazy:
Timescaledb achieved 6000x higher inserts, 5-175x faster queries, 150x-220x cheaper
Benchmarks open-source, methodology in post.
TimescaleDB vs. Amazon Timestream
21–30 of 203 posts
Re: TimescaleDB vs. Amazon Timestream
#22My takeaway from this is more to be wary of AWS than anything.
I've also heard gcp can be a real mess.
Is Azure any good yet?
Re: TimescaleDB vs. Amazon Timestream
#23I can't get over the fact that they first say: "Amazon has a history of offering services that take advantage of the R&D efforts of others: for example, Amazon Elasticsearch Service, Amazon Managed Streaming for Apache Kafka,[...]" And at the end of the article they promote how they themselves rely on other people hard work: "TimescaleDB uses a dramatically different design principle: build on PostgreSQL. As noted pr…
Except timescaledb is open source: https://github.com/timescale/timescaledb
This GitHub repository is just the database, what about the code that holds together their cloud resources? I was not able to find it.
They criticize AWS for making money on Elasticsearch for example, AWS is "taking advantage of the R&D efforts of others". So Amazon is making money on a "serverless" / cloud experience. At the same time, it is known that Amazon is contributing back to Elasticsearch [1]. To that regard, I find their business model really similar to the one AWS is relying upon.
[1] https://www.techrepublic.com/article/aws-contributes-to-elas...
Re: TimescaleDB vs. Amazon Timestream
#24I can't get over the fact that they first say: "Amazon has a history of offering services that take advantage of the R&D efforts of others: for example, Amazon Elasticsearch Service, Amazon Managed Streaming for Apache Kafka,[...]" And at the end of the article they promote how they themselves rely on other people hard work: "TimescaleDB uses a dramatically different design principle: build on PostgreSQL. As noted pr…
Timescale is a freely available PostgreSQL extension built in the open, and anyone can contribute. That's one of the great things about PostgreSQL - it was built to be extensible and allow customization. YAY!
Again, you're free to use it for any project, all Community features, wherever you want. The only thing you can't do is run a DBaaS for TimescaleDB. Seems like a fair tradeoff, right?
Re: TimescaleDB vs. Amazon Timestream
#25Under what circumstances would TimescaleDB be a poor choice for a company already using postgres at this point?
Re: TimescaleDB vs. Amazon Timestream
#26I can't get over the fact that they first say: "Amazon has a history of offering services that take advantage of the R&D efforts of others: for example, Amazon Elasticsearch Service, Amazon Managed Streaming for Apache Kafka,[...]" And at the end of the article they promote how they themselves rely on other people hard work: "TimescaleDB uses a dramatically different design principle: build on PostgreSQL. As noted pr…
I think we (like many) stand on the shoulders of giants when it comes to software, but I’m not sure the comparison is quite apt.
Amazon primarily runs and monetizes closed-source, SaaS-only managed services.
TimescaleDB instead is implemented in the open as an extension to PostgreSQL, and enriches and benefits the broader PostgreSQL community by unlocking a new use case (time series). The Postgres extension framework exists very much for this purpose, for projects like TimescaleDB to contribute back without needing to “pollute” mainline with domain-specific features. Most of TimescaleDB’s code (and all development for the first few years) is Apache 2, and all features are free for anybody to self-manage.
(Disclaimer: I work at Timescale)
Re: TimescaleDB vs. Amazon Timestream
#27Not 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…
What kind of auth & logging does TimescaleDB offer? Is every request authenticated & authorized?
Re: TimescaleDB vs. Amazon Timestream
#28My takeaway from this is more to be wary of AWS than anything. I've also heard gcp can be a real mess. Is Azure any good yet?
Depends on what type service you trying.... We do face few hiccups now and then.. but overall okay..
Rather i would recommend to go with architecture that is not tightly coupled to certain vendor and built on open source products...
We also prefer/buy services from companies who build OSS like in case of ELK, we, rather than hosting and doing it by ourselves. We are more than happy to pay bit more for hard work their team has done.
Re: TimescaleDB vs. Amazon Timestream
#29Earlier quoted context omitted.
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…
But you can just run timescaleDB inside your amazon VPC. No need to use their services at all.
And we in fact have fully open-source/free k8s helm charts to easily spin up TimescaleDB, including with HA and automated failure detection/failover and streaming replication for incremental backups:
https://github.com/timescale/timescaledb-kubernetes
Or just use Timescale's managed cloud on AWS:
Re: TimescaleDB vs. Amazon Timestream
#30Not 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…
I completely agree I think you misunderstood me.
I would like to see comparisons between Timescale and Druid.
I already know Timestream isn't up to the task lol.