pierregillesl
Joined 11 years ago
Joined 11 years ago
SQLite and DuckDB solve different problems and actually complement each other quite well. SQLite is excellent for transactional workloads (OLTP), while DuckDB shines for analytical workloads (OLAP), especially time-series data and aggregations.
We’ve been using both side-by-side in an open-source project for about two years: SQLite for configuration and transactional data, DuckDB for historical sensor data and analytics. So far, it’s been a very good combination.
It's less "techy" than HA (no YAML files, no CLI), and UI first.
We have way less integrations for now, but are working hard on it.
Don't hesitate to try it and make us some feedback.
I'm the core maintainer of an open-source smart home software (https://github.com/GladysAssistant/Gladys, 2.2k stars, has been existing since 2014), and is not listed, any reason why? :)
In my experience, as soon as there is some new data coming in the DB, the .backup command will continue, and if the writes are not stopping, the backup will never stop as well :D
In Gladys case, we put in the application logic a blocking transaction to lock writes during the backup. I haven't found any other way to avoid infinite backups in case of write-heavy databases
Learned that the hard way when implementing sqlite3 backups on Gladys Assistant ( open-source home automation platform https://github.com/GladysAssistant/Gladys )
Gladys was designed from the beginning to be a consumer software, meaning: no SSH needed, no files to edit, no “you-need-to-configure-grafana”.
Everything happens in a very simple UI that the whole family can use, that’s our end goal :)
So I would say it’s 2 differents philosophy
https://gladysassistant.com/blog/integrate-node-red-with-gla...
More on https://gladysassistant.com/ Twitter: @pierregillesl