Hacker News new | past | comments | ask | show | jobs | submit login

Hi, I authored this post, but the credit really goes to the Timescale database team.

Multi-node TimescaleDB is the result of a massive amount of engineering effort over two years, as can be seen in this +67,000 line PR: https://github.com/timescale/timescaledb/pull/1923

We're thrilled to make this free so that more developers can use it.

Am i the only one who thinks it is really cool that this will be free but hesitant to use it?

I have seen so many distributed data storages fail in a multitude of ways that i just dont trust anyone anymore. After 2-3 years they may have ironed out most bugs and i can evaluate again whether i do trust their implementation to store my data safely.

This is why we built this on top of Postgres. It allows us to inherit Postgres reliability.

While I can't guarantee there won't be bugs ;-), we have found that building on Postgres has enabled a much higher level of reliability than other time-series databases.

One thing to recognize that the lowest-level storage guts of TimescaleDB is Postgres, which really provides a super-stable, reliable foundation. This obviously doesn't avoid all distributed bugs, but it's a huge benefit.

It's also the case that TimescaleDB provides real benefit and scale even in "single-node" form, which allows for traditional primary/replica replication (for fault tolerance / HA / read replicas and scaling), especially when coupled with our native compression.

So we have users storing 100s of billions of rows in hypertables in the non-distributed version of TimescaleDB as well, including in our fully managed cloud service.

I would add your GitHub org in the "community" link of your site/blog. I was trying to get to the code from there and couldn't find a link.

I'll be looking forward to playing around with this. thanks...

Thanks for the feedback!

that's a strange KPI to tout.

It's definitely not a KPI. But still representative of the amount of work that has gone into this!

I'm not sure a 67k line PR proves anything more than 'noone really reviewed this'.

Or that there was a huge development effort going in a private branch that had PRs and code review for each of the 226 commits :)


Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact