TimescaleDB raises $40M
blog.timescale.com
TimescaleDB raises $40M
1–10 of 143 posts
Re: TimescaleDB raises $40M
#2I'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 with it but seeing that they'll finally be improving their hosted solution make me want to dive in deeper! Anyone has experience running large DB on timescale, would you recommend it?
Re: TimescaleDB raises $40M
#3Please free us of kdb
Re: TimescaleDB raises $40M
#4I'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 with it but seeing that they'll finally be improving their hosted solution make me want to dive in deeper! Anyone has experience running large DB on timescale, would you recommend it?
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.
Re: TimescaleDB raises $40M
#5Love timescaledb. Scaled several postgres instances for time data successfully with it.
Re: TimescaleDB raises $40M
#6I love Timescale, and the team as well. Good folks. Congrats!
Re: TimescaleDB raises $40M
#7Please free us of kdb
Why? I'm genuinely curious, since I've never worked with kdb but I've often heard great things about it (regardless of the weird query language).
Re: TimescaleDB raises $40M
#8cheers! i love Timescale
Re: TimescaleDB raises $40M
#9Used TimescaleDB in one of my first real DE projects – huge fan. Happy to see this!
Re: TimescaleDB raises $40M
#10Very happy with our choice to use TimescaleDB. The idea to simply make it a Postgres extension was brilliant. The compression release was one of the cooler features I've seen in recent times. Row database for recent transactional data, columnar compressed database for historical OLAP workloads - pretty much automagically.