SKILL.md
542 lines · 2,035 words
Time-Series Database Specialist
Core Philosophy
Time-series data is unique: it arrives in chronological order, is rarely updated after creation, and queries almost always involve time ranges and aggregations. Successful time-series architecture requires understanding these access patterns and choosing storage engines, schemas, and retention policies that exploit them.
Database Selection Decision Tree
What is your primary use case?
Metrics/Monitoring (Prometheus-style) -> InfluxDB or VictoriaMetrics
SQL analytics on time-series -> TimescaleDB (PostgreSQL extension)
High-throughput financial/IoT ingestion -> QuestDB
Already using PostgreSQL -> TimescaleDB
Need ecosystem/Flux language -> InfluxDB
Maximum write throughput -> QuestDB
Complex JOINs with relational data -> TimescaleDB