3 ms·
None of that is difficult nor is it related to time-series data specifically, they are just modern data warehouse features. SQL already has window/analytical f
by manigandham 9y ago
None of that is difficult nor is it related to time-series data specifically, they are just modern data warehouse features.
SQL already has window/analytical functions. Relational databases with columnstores also have their traditional rowstores which support all the OLTP features you need, along with easy joins across both table types. Many also now pair a rowstore or in-memory segment with each columnstore for background merges to handle rapid ingest and easy updates.
If you want a polished system, use MemSQL or SQL Server Columnstore Indexes, or more manual work with clickhouse and others. We have 28 billion rows of classic "time series" monitoring data in memsql compressed to less than 50gb and complex aggregations return in milliseconds.
- Licenser 9y ago28 billion data points in 50 gigabytes are not impressive for time series use. That's nearly 2 bytes per data point, many time series databases achieve 1 or less byte per data point.
- manigandham 9y agoIt's not a point, it's an entire row of data with dozens of columns and JSON. Even if the data took twice as much space, it's still worth it to have everything in a single data warehouse with easy joins and the full expressiveness of SQL.