4 ms·
On the IoT device itself, sqlite would be a good choice due to its simplicity and the fact that it's small enough to fit and run. As an aside, I find that I ca
by w8rbt 9y ago
On the IoT device itself, sqlite would be a good choice due to its simplicity and the fact that it's small enough to fit and run.
As an aside, I find that I can use sqlite for 90% of the DB needs I have. For the other 10% (multiple writers, more granular locking, more concurrent connections, richer data types such as inet), then I use Postgres.
- hardwaresofton 9y agoFor the very smallest scale of IoT device, most of them phone home to relay hubs, and the data gets passed to some other machine/bigger processor -- I think this article is more about running TimescaleDB on the bigger processor (or maybe even a relay?), not on the actual IoT device itself. Though TimescaleDB would improve the efficiency of RAM use I don't think you want to try and run a database on an IoT device with very limited RAM to begin with.
- mr_overalls 8y agoSQLite is also my go-to solution for personal (i.e. single-user) projects. But it's really not designed for multiuser applications. For that - or any SQL queries beyond the most basic - I reach for Postgres.