Live data from Hacker News

Amazon Timestream – Fast, scalable, fully managed time series database

aws.amazon.com

21–30 of 131 posts

Re: Amazon Timestream – Fast, scalable, fully managed time series database

#21
post #4

Seems positioned to compete with Azure Data Explorer (MSFT's log/time series optimized service). I know Azure runs a lot of services on top of Data Explorer (previously called Kusto) I wonder if this is a true internal battle tested product or a me-too offering.

I use Kusto daily and it is by far my favorite dev tool. It's incredibly fast and actually fun to use. I'm interested to compare it to Timeseries.

Kusto is still the name of the query language and the desktop application (Kusto.Explorer), the service was just renamed to Azure Data Explorer.

Re: Amazon Timestream – Fast, scalable, fully managed time series database

#22
post #9

Honest question: when dealing with time-series data, do you actually need every data point? Is that level of granularity really necessary? IMO, it makes way more sense to decide the aggregations you want ahead of time (e.g. "SELECT customer, sum(value) FROM purchases GROUP BY customer"). That way, you deal with substantially less data and everything becomes a whole lot simpler.

Sure you can do if you're really sure that you won't need to group by something else later. You wouldn't want to store more granularity than necessary but you can't go back in time to get a data point you didn't store.

Re: Amazon Timestream – Fast, scalable, fully managed time series database

#24
post #4

Seems positioned to compete with Azure Data Explorer (MSFT's log/time series optimized service). I know Azure runs a lot of services on top of Data Explorer (previously called Kusto) I wonder if this is a true internal battle tested product or a me-too offering.

I might be mistaken but wouldn't Data Explorer be more similar to AWS CloudWatch which has been around for a long time.

Re: Amazon Timestream – Fast, scalable, fully managed time series database

#25
post #22
post #9

Honest question: when dealing with time-series data, do you actually need every data point? Is that level of granularity really necessary? IMO, it makes way more sense to decide the aggregations you want ahead of time (e.g. "SELECT customer, sum(value) FROM purchases GROUP BY customer"). That way, you deal with substantially less data and everything becomes a whole lot simpler.

Sure you can do if you're really sure that you won't need to group by something else later. You wouldn't want to store more granularity than necessary but you can't go back in time to get a data point you didn't store.

In that case, can you just store each data point in a data lake somewhere and do a batch-job? Apache Flink supports this use case as well as real-time.

Re: Amazon Timestream – Fast, scalable, fully managed time series database

#29
post #14

jesus christ six amazon articles in a day? AWS is undeniably the body of christ for HN but am i missing something? FSX, blockchain, timestream, Graviton, ground station, and cloudwatch... all of these articles are advertisements for mundane shit.

There will be a lot more. The keynote today still has an hour left, and there is two more hours of keynotes tomorrow.

(Written from keynote floor)

Post reply on HN