5 ms·
If AS OF is a dealbreaker for you, so be it, but I think TimescaleDB is trying hard to be more than a "simple timeseries" aggregator like so many competitors. W
by claytonjy 6y ago
If AS OF is a dealbreaker for you, so be it, but I think TimescaleDB is trying hard to be more than a "simple timeseries" aggregator like so many competitors. We're using it to store hundreds of millions of complex IIOT data packets, where a fully normalized packet adds dozens of rows across ~4 tables.
Having it be mostly plain-ol-postgres has been huge for designing and evolving the data model in a way that I'd hate to do without "real" SQL.
- snidane 6y agoI'm sure your product is great for many customers in their domains. The asof and other time based joins are a necessity for just slightly more complicated data processing than just a trivial aggregation at the tail of the stream which is majority of use cases in IOT and real time monitoring. Without that I can pipe my data to /dev/null giving me even better write performance while also not being able to solve this common financial industry use case.
- claytonjy 6y agoSorry, didn't mean to imply I work there, I don't; my employer uses Timescale and I designed our schema. Timescale has been quite performant for us fetching arbitrary past time windows, but I'll stop the cheerleading there as I think mfreed covered the details far better. I'd certainly still like to see AS OF support!