Amazon Timestream vs FiloDB

Amazon Timestream is a managed cloud service offering time-series database engines for low-latency queries and large-scale ingestion. Timestream for LiveAnalytics scales ingestion, storage and query capacity independently and can process millions of queries. Memory and magnetic tiers support retention rules that move data and delete older records. Timestream for InfluxDB 3 Enterprise supports clusters of up to 15 nodes assigned to ingestion, query or compaction work. Backups can run hourly, daily, weekly, monthly or on a custom cron schedule, with retention from one to 365 days; on-demand backups can remain for up to 3,650 days. AWS states that data is encrypted by default and documents IAM, KMS and AWS Backup integrations. Ingestion options include SDKs, CLI, WriteRecords API, Lambda, IoT Core, Kinesis, MSK, Managed Service for Apache Flink and Telegraf. SQL, Flux and InfluxQL are supported query languages.

FiloDB is a free, Apache-2.0 open-source database for distributed, real-time time-series, event, and operational data. It is designed to ingest and query many millions of time series, sharding data across processes with distributed querying. Columnar compression and off-heap memory management support substantial in-memory storage while reducing garbage collection. PromQL is available through an HTTP API and command-line interface; the README describes support as about 60%. Histograms are a first-class column type, with the project reporting possible compression and query-speed improvements of up to two orders of magnitude. Typical ingestion uses Apache Kafka, while the Gateway accepts Influx Line Protocol over TCP. Grafana can connect through the Prometheus-compatible API, and Cassandra is identified as the persistence store. Deployment uses clustered standalone processes and requires Java, Cassandra, Kafka, Rust, a C compiler, and SBT to build.