On: TimescaleDB vs. Amazon Timestream

[rattray]

My 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?

[ameyv → rattray]

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.

[dumbfounder → ameyv]

That is not the mantra at our company. We want serverless and managed services whenever possible because getting resources to setup and maintain anything is next to impossible. We are now trying to use some competing products to AWS products that are full SaaS, so theoretically great, but because it isn't tacked on to our AWS bill it is very hard to get it approved and we are waiting around for weeks turning into months.

[ameyv → dumbfounder]

I'm not saying you should not! But lets just say you want ELK stack, you can try ELK cloud from Elastic which is hosted on AWS or Azure Or GCP as managed services But Elastic company manages it...That also help those folks support themselves.

[dumbfounder → ameyv]

Hosted on AWS does not mean it gets wrapped up in the AWS bill. Which means we need to sign a separate contract, which is painful to make happen.

[mcqueenjordan → rattray]

The core services are really good, and I tend to stick to those.

For me, my list is: IAM, STS, Route53, EC2 (and all of its children), S3, and SQS.

(By the way, hello fellow T-bird.)