News for hackers. Stuff that matters.
Re:It’s About Time for Time Series Databases by kodablah on Thursday January 25, 2018 @08:44AM (#16230684)
Sorry to leave the technical detail part real quick. But is anyone else concerned about using a DB solely from a company built specifically around that DB? After Rethink DB (sustainability issue) and Foundation DB (bought and shuttered/hidden) and Riak (admittedly haven't kept up but I saw [0]), I am wary of using any DB that is not built by a large community or is not built as a non-core project from a large tech company. Sorry TimescaleDB, I see you have raised a decent amount of funding, but I have to choose my DBs w/ trepidation these days.

0 - https://www.theregister.co.uk/2017/07/13/will_the_last_perso...

Re:It’s About Time for Time Series Databases by lbruder on Thursday January 25, 2018 @10:58AM (#16231717)
We use a combination of SQLite and a sharding frontend service. One SQLite database file per device, one table per sensor, table contents are timestamp and measured value. As simple as it gets, easy to scale, and damn fast.

But try telling people you're using SQLite to store critical data...

Re:It’s About Time for Time Series Databases by wenc on Thursday January 25, 2018 @12:30PM (#16232639)
That's a good pattern for straight data retrieval.

Unfortunately if you need to do aggregated queries on all of the SQLLite tables, things may be challenging.

But if you could somehow connect Spark to a folder (on a distributed FS) of these SQLite files...

Edit: Also SQLite has a limitation that only one process can write to it at a given a time. For this particular use case though, it shouldn't be a problem unless you have rewrites coming from various sources (which can happen when correcting data)

Re:It’s About Time for Time Series Databases by foota on Thursday January 25, 2018 @02:33PM (#16233822)
I mean, depends on the aggregation you need imo. Shouldn't be too hard (tm) to rig up some distributed query pipeline. (as long as you are ok with coding per query, instead of the convenience of sql)
Re:It’s About Time for Time Series Databases by baldfat on Thursday January 25, 2018 @12:02PM (#16232382)
> But try telling people you're using SQLite to store critical data...

SQLite is solid and trusted by many but for some unknown reason some people refuse to see it as a solution for their needs. I have seen many databases that could easily been replaced by SQLite.

Re:It’s About Time for Time Series Databases by wenc on Thursday January 25, 2018 @01:11PM (#16233023)
I looked into SQLite a while ago, and it wasn't so much its robustness that was the deal-breaker, but more the fact that it couldn't handle writes from parallel processes from multiple users (i.e. concurrency) like a normal SQL database could.

I see SQLite as a file-format with a SQL interface.

Re:It’s About Time for Time Series Databases by amyjess on Thursday January 25, 2018 @05:13PM (#16235204)
> I see SQLite as a file-format with a SQL interface.

I love the description from SQLite's website on the subject:

> SQLite does not compete with client/server databases. SQLite competes with fopen().

https://www.sqlite.org/whentouse.html

Re:It’s About Time for Time Series Databases by da_chicken on Thursday January 25, 2018 @02:52PM (#16233990)
Yep. Parallel performance is the biggest issue I've seen with SQLite.

SpiceWorks is the biggest example of a product that doesn't scale because they've elected to use SQLite (and only SQLite). There's no hard limit on the number of devices, but most people say not to exceed about 1,000 devices. We tested it out against 800 devices. We started it on Friday. On Monday, it was still running.

The only other issue I've seen with it is with the data typing. Type inference is much weaker than strict typing, and sometimes it doesn't quite store things the way you'd expect. Granted, the last time I saw problems with that was years ago, but I've seen it.

Re:It’s About Time for Time Series Databases by baldfat on Thursday January 25, 2018 @03:54PM (#16234569)
There are plenty of problems that don't need parallel performance.
Re:It’s About Time for Time Series Databases by da_chicken on Thursday January 25, 2018 @04:45PM (#16234990)
And there are plenty that do. What's your point?
Re:It’s About Time for Time Series Databases by mixmastamyk on Thursday January 25, 2018 @05:08PM (#16235162)
Because some won’t consider sqlite even for those that don’t.
Re:It’s About Time for Time Series Databases by dfox on Thursday January 25, 2018 @02:12PM (#16233602)
There is Berkeley DB/SQL (now sadly owned by Oracle), which is essentially Sqlite with BDB instead it's original B-tree implementation, that supports multiple parallel writers. Also Firebird can be used as in-process embedded database and supports multiple writers (in fact in the server mode it uses same file-locking based synchronisation mechanisms as in embedded mode)

On the other hand it is somewhat rare to see aplication that really needs multiple writers and would not be better served by full fledged database server.

Re:It’s About Time for Time Series Databases by fpoling on Friday January 26, 2018 @07:25AM (#16238608)
Berkley DB is not as reliable as SQLite. Subversion, before switching to own storage, where known for data corruption problems attributed to Berkley DB.
Re:It’s About Time for Time Series Databases by amyjess on Friday January 26, 2018 @10:33AM (#16239888)
I remember the old days when people would refer to berkdb as "Berserkley" because it tended to go berserk on your data. It's always had a bad reputation for reliability.
Re:It’s About Time for Time Series Databases by xapata on Friday January 26, 2018 @10:26PM (#16244675)
It can handle some degree of concurrency via threading.
Re:It’s About Time for Time Series Databases by dominotw on Thursday January 25, 2018 @01:14PM (#16233043)
probably cos of word "Lite" in their name.
Re:It’s About Time for Time Series Databases by gregmac on Thursday January 25, 2018 @11:23AM (#16231962)
Wow, that's a pretty neat approach. I have a bunch of questions, if you don't mind..

Do you do filesystem replication or something else for HA? Is this running in one of the cloud cloud IaaS providers or something else?

Why did you go with this approach? Eg: Was it a deliberate decision after evaluating other options, a "this is what we know" type situation, or did it grow organically from something smaller?

How long has it been running? Whats the rough size of data you have (GB/TB, number of servers, number of DB instances)? Any reliability problems?

If you were building this service from scratch, would you do it this way again?

Re:It’s About Time for Time Series Databases by lbruder on Thursday January 25, 2018 @03:33PM (#16234374)
Don't mind at all. ATM we're using a simple VMWare server backing up the virtual HDD every night, with a dirty hack thrown in (no full backups on weekends as that's when the bigger jobs run, so I dump the current day to a CSV on a smaller virtual HDD that's still saved daily). We're running on our own systems as our customers are pretty paranoid about where their data is sent.

The history of this system is pretty organic, lots of experimentation. Started with Postgres, but that was too slow if a select statement returns tens of thousands of rows. MariaDB was way faster but became erratic once we passed about 2 billions of records. Now with SQLite we are at about 180 GB, about three years of data so far, so not really "big data" territory yet.

Constantly looking for better alternatives. InfluxDB looks promising, but maybe we'll switch to a "hot/cold" approach instead, keeping whole "cold" days as JSON objects in JSONB fields in Postgres again while storing "hot" data in SQLite. We'll see...

So far the system has been rock solid. In the last few weeks we went live for real, now storing about 2k records a second. Not a problem so far.

Re:It’s About Time for Time Series Databases by kgc on Thursday January 25, 2018 @08:58PM (#16236479)
Wait, so to be clear, you moved from PG > Maria > SQLite?
Re:It’s About Time for Time Series Databases by srcmap on Thursday January 25, 2018 @11:11AM (#16231848)
Just tell them SQLite is used by ALL Android / iOS phones (billions of them) to store user's critical data.

I have not heard of any cases of SQLite failure in phone, or anyone needing a DB admin to recover their phone contact data.

Re:It’s About Time for Time Series Databases by j_s on Thursday January 25, 2018 @11:23AM (#16231961)
> I have not heard of any cases of SQLite failure in phone, or anyone needing a DB admin to recover their phone contact data.

For a long time (until API level 11), Android automatically silently deleted corrupted SQLite databases. https://android.stackexchange.com/questions/12388#33896 https://stackoverflow.com/questions/7764943

I learned the hard way to limit SMS storage and install Jan Berkel's SMS Backup+ https://github.com/jberkel/sms-backup-plus/#readme after losing my first Android SMS database (this may or may not have been SQLite's fault).

https://www.sqlite.org/howtocorrupt.html#_bugs_in_sqlite

Re:It’s About Time for Time Series Databases by j_s on Thursday January 25, 2018 @01:25PM (#16233162)
Specifically (can't edit above post -- too slow):

https://issuetracker.google.com/issues/36911900#comment457

>the SQLite packaged with Android is being upgraded to version 3.6.22 in Android 2.2. I think that the SQLite database corruption bug linked in comment 451 has been fixed in Android 2.2. So _if_ that's what's causing the text message database corruption and deletion, then this bug will probably be fixed in Android 2.2

http://sqlite.1065341.n5.nabble.com/Android-database-corrupt...

>Statically link your application against SQLite 3.6.23 instead of using the SQLite 3.5.9 that is found on Android. The bug you are hitting was fixed in SQLite 3.6.2

Contrast https://web.archive.org/web/20110219041419/https://www.sqlit... (Feb 2011) vs. https://web.archive.org/web/20110729152833/https://www.sqlit... (July 2011), which could be a glitch in the Internet Archive (a partial copy of the oldest record?) but adds "Though SQLite is resistant to database corruption, it is not immune" and introduced an extensive history of known issues.

Sqlite is amazing and its development history is further testament to its current reliability, especially when used correctly!

Re:It’s About Time for Time Series Databases by PaulRobinson on Thursday January 25, 2018 @11:27AM (#16231992)
SQLite was built as a solution to the question "How do we put a SQL database on a nuclear submarine stealthily moving away from base for months at a time in secret, without putting a DBA in there with it?"

It can go wrong, it does go wrong, but it's a pretty solid solution, especially if you're not needing insane concurrency throughput.

The problem is many people need concurrency. They're running web apps over multiple servers. It's there where SQLite is a problem.

Re:It’s About Time for Time Series Databases by seangrogg on Thursday January 25, 2018 @12:47PM (#16232793)
Source for origin? Legit interested.
Re:It’s About Time for Time Series Databases by j_s on Thursday January 25, 2018 @01:01PM (#16232935)
https://en.wikipedia.org/wiki/SQLite#History

>used aboard guided missile destroyers [...] operated without installing a database management system or requiring a database administrator

PS. Thanks to your question, today I re-discovered https://unqlite.org, which may fulfill a requirement I've been facing for some time. Awesome!

Re:It’s About Time for Time Series Databases by seangrogg on Monday January 29, 2018 @04:27PM (#16260755)
Hey hey, unqlite looks pretty interesting. I'm both glad you were able to rediscover it and glad that I can have fun reading about it!
Re:It’s About Time for Time Series Databases by otterley on Thursday January 25, 2018 @11:10AM (#16231829)
What's your replication/HA story?
Re:It’s About Time for Time Series Databases by j_s on Thursday January 25, 2018 @11:20AM (#16231917)
Yes, collecting/aggregating for querying seems like the sticking point.
Re:It’s About Time for Time Series Databases by tzakrajs on Thursday January 25, 2018 @04:00PM (#16234624)
What does collecting or aggregating have to do with replication/HA?
Re:It’s About Time for Time Series Databases by j_s on Thursday January 25, 2018 @04:13PM (#16234726)
It was my improvisational approach to pointing in the right direction. https://en.wikipedia.org/wiki/Yes,_and....

I don't really see how replication/HA is an issue in this setup beyond normal file system replication/HA (which seems to be a solved "spend money on NAS" problem in the enterprise world). If your filesystem isn't reliable / delivering what's needed then you're gonna have a bad time no matter the storage approach; I doubt some unusual option is involved though it would be cool to be proven wrong.

The only time the filesystem could even potentially have read/write conflicts (assuming 1-to-1 correlation between devices writing to files) is when querying. I did wind up muddling the terminology in the interest of jumping to the actual problem.

Re:It’s About Time for Time Series Databases by tomc1985 on Thursday January 25, 2018 @09:01PM (#16236488)
Wouldn't be hard to rsync that data to rotating s3 buckets/nfs shares/ftp drops/whatever
Re:It’s About Time for Time Series Databases by otterley on Tuesday January 30, 2018 @12:35PM (#16267133)
Those are backups/DR. HA is for when a database instance fails so you can keep on trucking as though nothing happened.
Re:It’s About Time for Time Series Databases by creeble on Thursday January 25, 2018 @11:25AM (#16231971)
Simpler than a log file? What's the significant advantage of SQLite vs just appending to a file?
Re:It’s About Time for Time Series Databases by eloff on Thursday January 25, 2018 @12:27PM (#16232601)
Transactions? Crash data safety? SQL queries? Portability?
Re:It’s About Time for Time Series Databases by creeble on Thursday January 25, 2018 @02:58PM (#16234038)
I don't see how any of those apply for a two-column 'db' of timestamp and data.
Re:It’s About Time for Time Series Databases by jmkirby on Thursday January 25, 2018 @04:00PM (#16234619)
Except.. compliance staff who want to use some ahem wonderful standards complaint reporting tool.

There's just one solitary mention of Informix in the whole discussion, as I'm typing this. And that's a comment lumping Informix with everything else commercial and expensive.

I thought Informix owned the embedded dB space at a certain rollout complexity. Remember the backups... Informix speaks json too, including at some quite low level primitives. Whether you buy a product like Informix Edge plus tools or not, depends on what is sending the time series data.

Re:It’s About Time for Time Series Databases by rpedela on Thursday January 25, 2018 @05:52PM (#16235497)
It is database per device and table per sensor, not just one table. With SQL you can do joins, aggregations, etc. If you just want to log it, sure use a log file. As soon as you want to use the data somehow, you need SQL or your own log file parsing and query code. Personally, I rather just use SQL.
Re:It’s About Time for Time Series Databases by creeble on Friday January 26, 2018 @01:01AM (#16237319)
If you’re storing from multiple sensors with multiple write processess, you will have concurrency problems if they’re in the same db with SQLite.

I’m not referring to manipulating or even querying the data after it’s stored. I just don’t see how saving the original data in SQLite buys you anything, if it needs to be collected into a db for queries, etc, anyway.

Re:It’s About Time for Time Series Databases by rpedela on Thursday January 25, 2018 @11:32AM (#16232049)
SQL query support?
Re:It’s About Time for Time Series Databases by jstarfish on Thursday January 25, 2018 @12:35PM (#16232691)
Indexing.
Re:It’s About Time for Time Series Databases by jnordwick on Thursday January 25, 2018 @02:21PM (#16233675)
On disk support?
Re:It’s About Time for Time Series Databases by linsomniac on Thursday January 25, 2018 @10:06AM (#16231203)
There are tons of justifications you can come up with for not using something you don't want to use. The down side is that you aren't going to be getting the upsides you'd get if you used a new technology, possibly to the extent of being no longer competitive with people who do use that technology.

The important thing is balancing chasing the new hotness vs. always using the tried and true.

Last year I ran into a similar sort of situation at work, the funds to buy Ansible Tower required a battle I wasn't willing to fight. The argument was "We've spent so much money on tools that then get abandoned." We spent nearly a year with me being the only one in the company that could run Ansible playbooks because of this, until I finally found RunDeck. Now, we aren't paying for Rundeck, does that make it more likely to be abandoned? Was the risk in our operations if I suddenly became unavailable worth the saved licensing fees? Well, in this case it worked out ok, but it could have gone very badly.

As far as timeseries goes, there are huge advantages here. We used to use collectd/graphite/carbon, but a year or more ago I switched us over to InfluxDB/telegraf/grafana. It was a little rocky a start, the first version of Influx I used had plenty of problems. At the time Prometheus was probably a better choice, but I couldn't come up with a way to make it's pull-centric design fit into our environment. Then InfluxDB settled down and things have been great since.

We have way better metrics, with a way more usable dashboard, and significantly lower load. Literally, disabling collectd ended the complaints about performance on our dev/stg environments.

Re:It’s About Time for Time Series Databases by kodablah on Thursday January 25, 2018 @10:36AM (#16231483)
> The down side is that you aren't going to be getting the upsides you'd get if you used a new technology

True of course. I've found that at least "premature abstraction" is almost a requirement when using persistence. I'm not talking an ORM or anything, but put a service in front of it if you have multiple things needing it, or put an in-code abstraction if you don't. And make each abstraction's/service's operation very specific to its caller. So a simple "fetchMarketData(timeRange, tickerSymbols) -> StreamOfData" will save you so much in the future.

Re:It’s About Time for Time Series Databases by siculars on Thursday January 25, 2018 @09:51AM (#16231080)
Riak the database survives Basho the company. All assets (IP) were bought by bet365 (A large Basho customer) and made open source. Development continues.

/former Basho employee.

Re:It’s About Time for Time Series Databases by j_s on Thursday January 25, 2018 @10:42AM (#16231553)
> made open source

I hope things work out at least as well as they have for RethinkDB's resurrection/transition! The Riak Users mailing list seems like the best place to follow along: http://riak-users.197444.n3.nabble.com

https://github.com/basho/riak_kv/tree/develop-2.2.5 (November 2017)

http://bet365techblog.com/riak-workshop-summary (October 2017)

>the immediate goal of releasing a known good build as soon as possible [...] all code would be released under the Apache 2 license [...] contact the HLL developers to aid in the dependency and GPL removal

https://news.ycombinator.com/item?id=15182566#15183008 (September 2017)

>andrew_deane_: bet365 have signed the agreement to purchase all Basho IP [...] our intention is to open source all code, help rebuild the community and collaboratively take the development of RIAK forward

Re:It’s About Time for Time Series Databases by andrew_deane__ on Thursday January 25, 2018 @03:36PM (#16234404)
All IP has been made open by bet365 (including RIAK TS) and development is continuing, both in the community and within the company. bet365 are actively recruiting to support this effort, and are committed to the long term future of RIAK. Latest release is to be cut Jan / Feb with the help of the community.
Re:It’s About Time for Time Series Databases by hyder_m29 on Thursday January 25, 2018 @10:31AM (#16231438)
And RethinkDB has moved under the Linux Foundation.
Re:It’s About Time for Time Series Databases by walterbell on Thursday January 25, 2018 @08:51AM (#16230721)
Is the concern mitigated by this being an open-source Postgres extension? One question would be whether they have attracted external OSS contributors.
Re:It’s About Time for Time Series Databases by kodablah on Thursday January 25, 2018 @09:18AM (#16230868)
Depends on your reliance I suppose. Appears most of TimescaleDB's vendor-specific pieces are in the DDL area, but there are plenty of DML-specific extensions. I'm not saying TimescaleDB might not get to a level of maturity where I'd use it, I personally just can't justify it today. I've found DBs and ops/orchestration engines to be the most painful to move off from if you need to.
Re:It’s About Time for Time Series Databases by pas on Thursday January 25, 2018 @04:28PM (#16234840)
They also provide the most bang for the feature-complexity buck. (A DB is something you don't want to roll on your own, and you want to use the purpose-built one for your use case. A columnar store for time series, a scatter-gather SSD + random read optimized engine for hot OLTP, a fancy multi level cache/tier BLOB store for photos/files, CockroachDB for geo consistency, etcd for local consistent config, and so on.)
Re:It’s About Time for Time Series Databases by camel_gopher on Thursday January 25, 2018 @01:08PM (#16232997)
Data portability is certainly an important issue here to consider here given the points you mentioned. When adopting a vendor, the relevant question is "How much work is it to get data in?". And when planning for the contingency of vendor loss, the question is "How much work is it to get the data out?".

The first question is tied closely to the interfaces provided by the database, and those interfaces are usually commensurate with the associated tooling. In the case of time series databases, they include statsd, collectd, and good old JSON. Relational databases utilize SQL as expected. Take the example of migrating from Oracle to Postgres; you shouldn't have to spend an inordinate amount of retooling your applications because the data interfaces are similar.

Data egress is similar; SQL databases generally provide SQL/CSV exports, and most TSDBs (the good ones at least) allow you to get the data out via JSON through a REST interface.

Whether or not the DB you choose is open source, or from a small vendor, you should pick the right tool to solve your problem with data portability in mind. (disclosure, I work for http://irondb.io, and have used Postgres for 18 years)

Re:It’s About Time for Time Series Databases by greenleafjacob on Thursday January 25, 2018 @09:20AM (#16230873)
Basho is in receivership, close to bankruptcy. https://www.theregister.co.uk/2017/07/31/end_of_the_road_for...
Re:It’s About Time for Time Series Databases by btown on Thursday January 25, 2018 @09:48AM (#16231052)
For anyone just seeing this, its assets were purchased and are planned to be open-sourced: https://news.ycombinator.com/item?id=15182566
Re:It’s About Time for Time Series Databases by antirez on Thursday January 25, 2018 @09:26AM (#16230913)
What you say is another way to see the argument about OSS Project vs OSS licensed software which is actually a company and not a project.
Re:It’s About Time for Time Series Databases by qaq on Thursday January 25, 2018 @10:28AM (#16231397)
Timescale is open source PostgreSQL extension that is much safer vs RethinkDB.
Re:It’s About Time for Time Series Databases by tomc1985 on Thursday January 25, 2018 @08:59PM (#16236485)
Honestly I have found it is simply easier to master PostgreSQL and sqlite, and between the two (and with the right know-how) pretty much all use-cases are covered.

Played with a lot of databases, sql or no, and I always end up going back to PG

Re:It’s About Time for Time Series Databases by j_s on Thursday January 25, 2018 @10:36AM (#16231480)
There was a similar sub-discussion on the Datomic Cloud announcement last week: https://news.ycombinator.com/item?id=16168041#16168743

As an open source product it seems like TimescaleDB is less risky than Datomic. (Not that the comparison is even necessary -- I don't think they compete in the same category apart from both being non-relational DBs.)

[edit:link fixed, thanks! (and thanks for taking the time to correct my misunderstanding re:TimescaleDB as a relational DB)]

Re:It’s About Time for Time Series Databases by stalller on Thursday January 25, 2018 @11:25AM (#16231969)
Hi, the link you posted seems broken. Also just wanted to clarify that TimescaleDB is in fact a relational database, being built as a PostgreSQL extension. Looking at the nature of time-series workloads (namely appending data about recent events) we can architect the database differently for time-series workloads and applications powered by time-series data; scaling insert rates and storage capacity, increasing query performance and simplifying operations, while retaining full-SQL and the reliability of Postgres.
Re:It’s About Time for Time Series Databases by krylon on Thursday January 25, 2018 @10:14AM (#16231278)
> But is anyone else concerned about using a DB solely from a company built specifically around that DB?

It worked out pretty well for Oracle. (SCNR)

Re:It’s About Time for Time Series Databases by kodablah on Thursday January 25, 2018 @10:32AM (#16231439)
I'd almost rather be locked in to a cheap, may-deprecate DB than a really expensive one. The former at least forces you to move, the latter just costs your business a lot especially when non-doers run the tech show and will sink money over re-impl every time (as opposed to making measured decisions).
Re:It’s About Time for Time Series Databases by krylon on Thursday January 25, 2018 @11:09AM (#16231823)
FWIW, I found a table with prices for Oracle database licenses once, and it made Microsoft SQL Server look cheap. I am not sure if that means MSSQL is cheap, though. At least I am fairly confident that Microsoft is not going out of business anytime soon.

In my current job, I needed to get intimately familiar with the database our ERP software uses, because my boss needed lots of reports that the ERP software just did not do (unless paid an expensive consultant to customize the software for you). And the idea of having to move all that data to a different database makes me shiver in horror. I can understand why a business would be very reluctant to move their data from one database (both schema and engine) to another.

For business-critical tasks, I prefer a boring, reliable solution. But it is good to know that there are still interesting developments going on in the database area, building tomorrow's boring, reliable solutions.

Re:It’s About Time for Time Series Databases by Johnny555 on Thursday January 25, 2018 @03:17PM (#16234215)
There's also snowflakedb which was in the news today after getting a pile of funding. Though it seems to be cloud-only, not something you can run yourself.
Re:It’s About Time for Time Series Databases by kunthar on Thursday January 25, 2018 @06:14PM (#16235648)
riak is not dead and still have strong community of developers, users and enthusiasts. bet365 bought all the assets including enterprise parts and made them open source. you can join postriak slack channel and see with your own eyes there is active and vibrant community working about a lot of exciting features. so, no, party is not over yet!
Re:It’s About Time for Time Series Databases by Steeeve on Thursday January 25, 2018 @10:36AM (#16231481)
You mean like Oracle? Or Sybase? Or Informix? Or Terradata?

Well, I guess you can stick to DB2.

Re:It’s About Time for Time Series Databases by kodablah on Thursday January 25, 2018 @10:41AM (#16231539)
Having worked at places where they paid tons for options like those, and suffering from the inability to move and the difficulty of finding non-company tooling and community around them, I'd say they have the same problem. Point being: if your ecosystem is a single company, it's at the whims of that company's success and give-a-shitness. Non-DB companies and open source communities tend to gouge less and share more.
Re:It’s About Time for Time Series Databases by gaius on Thursday January 25, 2018 @09:17AM (#16230863)
If Timescale goes bust you still have all your data in Postgres, which isn’t going anywhere. The risk is much lower.