3 ms·

I'm pretty stoked for this. Timescale ability to use time series on a subset of tables (hypertables) really makes it an interesting choice. I've just dabbled wi

• eloff 5y ago
  I haven't tried running the distributed Timescale DB - in general more parts means more things to go wrong, so using their managed cloud service for that is a good idea. But I can attest that the single-server version is rock solid, just like PostgreSQL that it's based on. And it's free and source visible. The pace of innovation has also been really high, it just keeps getting better with every release.
• spmurrayzzz 5y ago
  If you end up transitioning to multinode deployments from a single node deployment, there are a bunch of tradeoffs to consider. A good reference point for this to check out the `multinode` label in their github issues. https://github.com/timescale/timescaledb/labels/multinode https://github.com/timescale/timescaledb/labels/multinode One of the big items that stood out to me is the inability to be able to migrate data from an existing table when creating a distributed hypertable. There were also some significant query performance reports as well. These all may improve with time of course, so watching the dev cycles will give you a good sense of that I think.