Three heretical opinions about the future of time-series data
summary
Claims three concrete heresies: all data is time-series, the common narrow name/tags/value model is wrong so use wide or nested schemas and joins, and SQL remains the lingua franca. Shows TimescaleDB built on PostgreSQL, with concrete performance claims (about 20x higher inserts vs Postgres, up to thousands-fold faster queries vs Cassandra, and a 3–5 node Timescale cluster beating a 30-node Cassandra cluster with 40% faster inserts at one‑tenth the cost).
AI-written summary · about
chapters (6)
- 0:00Start
- 1:16What you've been told
- 1:48Time-series data has a richer structure
- 1:58Fewer queries
- 2:15Leverage relations
- 4:00vs. PostgreSQL
related talks
39mTimescaleDB: Re-engineering PostgreSQL as a time-series database
51mPostgreSQL, The Time-Series Database You Want
51mBuilding a scalable time-series database on PostgreSQL
42mAccessible Time Series data
29mCatching Waves with Time-Series Data
13mTransform your business with time-series data (PRT061)
39mA New Data Model for Time Series Data Processing
30mCatching Waves with Time-Series Data