4 ms·
How does timescale (a single-purpose database) hold up against single-store (a multi-purpose database)? Of course, timescale is cheaper, but other than that, ha
by ignoramous 5y ago
How does timescale (a single-purpose database) hold up against single-store (a multi-purpose database)? Of course, timescale is cheaper, but other than that, have you folks compared / contrast against single-store as a TSDB?
PS https://www.timescale.com/papers/timescaledb.pdf https://www.timescale.com/papers/timescaledb.pdf is 404
- akulkarni 5y agoTimescaleDB performs quite well. One of our unique insights is that it is quite possible to build a best-in-class time-series database on top of Postgres (although it’s not easy ;-) Here is one benchmark: https://blog.timescale.com/blog/timescaledb-vs-influxdb-for-time-series-data-timescale-influx-sql-nosql-36489299877/ https://blog.timescale.com/blog/timescaledb-vs-influxdb-for-... There are some challenges with building on Postgres - but what we’ve been able to do is build innovative capabilities that overcome these challenges (Eg columnar compression in a row-oriented store, multi-node scale out). We also have some exciting things that we are announcing this week. Stay tuned :-) PS - Where did you find that PDF? Thought we took it down (it was hard to keep it up to date :-) )
- ignoramous 5y agoThanks. Re: paper: I stumbled upon it when going through other timescaledb threads on news.yc, specifically here, https://news.ycombinator.com/item?id=13943939 https://news.ycombinator.com/item?id=13943939 (5 yrs ago)