3 ms·
I evaluated InfluxDB at my previous company. Settled for TimescaleDB in the end due to the querying power of Postgres. Influx had some real quirks with nested
by odiroot 9y ago
I evaluated InfluxDB at my previous company. Settled for TimescaleDB in the end due to the querying power of Postgres.
Influx had some real quirks with nested queries (wrong data being returned). TimescaleDB is probably a bit slower and less compact but with our data (a few GBs/day) it wasn't our biggest problem.