Live data from Hacker News

Timescale, an open-source time-series SQL database for PostgreSQL

timescale.com

51–60 of 102 posts

Re: Timescale, an open-source time-series SQL database for PostgreSQL

#51
post #10

Any support for RDS? :)

We're talking with them...and you can help: https://github.com/timescale/timescaledb/issues/65

I submitted a request; my company's not huge but I hope it helps.

Timescale looks like the most promising replacement to InfluxDB on the market. Influx has been a source of pain, data corruption and other various issues; what a world it would be if we could use timescale!

The main blocker for us is Grafana support actually. I know Grafana is working on a Postgres connector; I am quite excited about this.

Re: Timescale, an open-source time-series SQL database for PostgreSQL

#52
post #48

I've come to rely heavily on Cassandra, but I miss good old SQL and adhoc functionality. Systems like Cassandra bring orher requirements when you need flexible data (Spark, for example), technical debt is always a worry for me. I want to give this a go for sure!

Hi, I'm curious what limitations you're running into with Spark SQL?

Re: Timescale, an open-source time-series SQL database for PostgreSQL

#53
post #29

Is the business model to charge for the clustering release?

Timescaler here. Although we haven't done any official announcements w.r.t. clustering, our plan is for this to be open source, like the single-node version.

Learning from the RethinkDB 'situation' [1] - do you have a viable business plan and are you monetising the database already?

1. https://news.ycombinator.com/item?id=12649414

Re: Timescale, an open-source time-series SQL database for PostgreSQL

#54
We have been using Postgres for a smaller event time series database (millions of rows) with good success. Tables are partitioned.

Some user reports (aggregations) are ~5secs so we batch-pre generate them currently.

Eeager to look into this to replace generation of reports with real time reports.

Re: Timescale, an open-source time-series SQL database for PostgreSQL

#55
post #48

I've come to rely heavily on Cassandra, but I miss good old SQL and adhoc functionality. Systems like Cassandra bring orher requirements when you need flexible data (Spark, for example), technical debt is always a worry for me. I want to give this a go for sure!

Hi, I'm curious what limitations you're running into with Spark SQL?

No limitations. Spark works and does a good job, it has many features that I can see us use in the future too.

With that said, it's yet another piece of tech that bloats our stack. I would love to reduce our tech debt: We are much more familiar with relational databases like MySQL and Postgres, but we fear they won't answer the analytics problems we have, hence Cassandra and Spark. We use these technologies out of necessity, not love for them.

Re: Timescale, an open-source time-series SQL database for PostgreSQL

#56
post #53

Earlier quoted context omitted.

Timescaler here. Although we haven't done any official announcements w.r.t. clustering, our plan is for this to be open source, like the single-node version.

Learning from the RethinkDB 'situation' [1] - do you have a viable business plan and are you monetising the database already? 1. https://news.ycombinator.com/item?id=12649414

We wouldn't do this if we didn't believe we could make a business out of it. That said, we are at a pretty early stage at this moment and are looking at many different options. As you may know, and if you've been following the discussions around business models for open-source projects, there are many approaches as well as challenges. All I can say is that we have been following the discussions and we are drawing lessons from past failures and successes.

Re: Timescale, an open-source time-series SQL database for PostgreSQL

#59

further evidence of how postgreSQL is eating noSQL. Every good concept first implemented in a custom noSQL solution eventually becomes an extension in postgres.

I also do the same when developing: Proof of concept in NoSQL, then go wild with the schema, then watch it become a horrible mess, then refactor into SQL (That being pg or mssql depending on the needs/politics)

Re: Timescale, an open-source time-series SQL database for PostgreSQL

#60
post #55

Earlier quoted context omitted.

Hi, I'm curious what limitations you're running into with Spark SQL?

No limitations. Spark works and does a good job, it has many features that I can see us use in the future too. With that said, it's yet another piece of tech that bloats our stack. I would love to reduce our tech debt: We are much more familiar with relational databases like MySQL and Postgres, but we fear they won't answer the analytics problems we have, hence Cassandra and Spark. We use these technologies out of ne…

Ah, I see -- so a thing that I'm curious about is, what do you miss about relational databases? Are they mainly aspects on the operational side, or the usability/API side?

Ultimately, the question that I'm interested in trying to answer is: would it help if there were more ways to make Spark feel like a traditional relational database? (e.g. being able to interact with the Spark driver using MySQL or Postgres wire protocol)

Post reply on HN