31–40 of 203 posts
I'm having a hard time understanding the cost comparison without details of the above. Are they saying that hosting your own cluster of timescaledb nodes within EC2 still comes in cheaper than timestream? This seems impossible, depending on the instance types of course.
Earlier quoted context omitted.
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…
Some people would want k8s, some docker swarm or whatever, some an aws config, others ansible, etc etc etc.
If I want a managed service, I _want_ to pay for that. The price includes people responding to pages and fixing problems, as well as fiddling with configs.
And I'd much rather be paying that money to a small (relatively) open-source company than a behemoth like AWS.
> 224x cheaper if you’re self-managing TimescaleDB on a VM I'm having a hard time understanding the cost comparison without details of the above. Are they saying that hosting your own cluster of timescaledb nodes within EC2 still comes in cheaper than timestream? This seems impossible, depending on the instance types of course.
Under what circumstances would TimescaleDB be a poor choice for a company already using postgres at this point?
Earlier quoted context omitted.
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?
Authentication to the database is typically governed to different security mechanisms, including certificate-based auth, password via SSL, etc.
Earlier quoted context omitted.
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…
Huh? If I want to run someone else's software on my cloud, how I want to do that depends on my cloud. I want docs and binaries, not a full cloud configuration. Some people would want k8s, some docker swarm or whatever, some an aws config, others ansible, etc etc etc. If I want a managed service, I _want_ to pay for that. The price includes people responding to pages and fixing problems, as well as fiddling with confi…
Is this not what S3 is? You are free to use Elasticsearch and handle everything yourself, but if you want a managed service, you can use AWS. They are "attacking" the S3 offering, I still struggle to see any difference with them hosting Postgres.
> And I'd much rather be paying that money to a small (relatively) open-source company than a behemoth like AWS.
I am 100% with you on this, I do not want to defend AWS nor do I want to promote their products. The vendor lock-in situation you are in when using AWS is pretty bad and quite scary... An yes, I agree that the way they monetize open-source software is questionable.
> 224x cheaper if you’re self-managing TimescaleDB on a VM I'm having a hard time understanding the cost comparison without details of the above. Are they saying that hosting your own cluster of timescaledb nodes within EC2 still comes in cheaper than timestream? This seems impossible, depending on the instance types of course.
AWS use to be great when it first came out in 2006ish, but now it is just because a pain to work with.
EDIT: especially considering all the other options are available in VPS now days.