TimescaleDB vs Alopex Skulk

What TimescaleDB is

TimescaleDB is a time-series database that runs as a PostgreSQL extension. Time series and event data are handled with plain PostgreSQL SQL.

How it works

Hypertables: PostgreSQL SQL tables partitioned by time automatically. The partitions are called chunks, and queries run on the relevant chunks.
PostgreSQL extension: TimescaleDB is installed and used as a PostgreSQL extension.
Row and columnar storage (Hypercore): new data lands in row form and is converted automatically to a compressed columnar form.

Main features

A function that aggregates by time buckets (time_bucket).
Aggregates refreshed in the background as new data arrives (continuous aggregates).
Retention policies that delete old data on a schedule.

Limits

It requires running a PostgreSQL server and installing the extension. Some features are offered under the Timescale License, separate from Apache 2.0. Adding PostgreSQL for metrics means one more database to operate.

How it differs from Alopex Skulk

Both partition time series by time and aggregate them with SQL.

Alopex Skulk is a time-series engine written in Rust that grows from embedded to server to cluster on the same engine. Start small by embedding it in your application, then move the same application to a server with Prometheus-compatible endpoints and to a cluster that scales out with sharding and replication. In every form it ingests time series, queries them with PromQL and SQL, stores them in time-partitioned, columnar Parquet files, and drops expired partitions automatically. The same engine runs embedded or as a server, with PromQL queries and no PostgreSQL added.

Try Alopex Skulk to grow time-series storage and aggregation from embedded to cluster on one engine. Start from Alopex Skulk.

References

TimescaleDB (GitHub), Hypertables, Hypercore, Continuous aggregates, Time buckets, Data retention, Timescale License