Alternatives to M3DB

Open-source distributed time-series database built for billions of metrics at scale. The listings below can replace it for an important use case. Each note says what changes if you switch.

The original

Replacements

Listings that take over the same core job as M3DB.

  • VictoriaMetrics

    Store and query monitoring metrics in a time-series database.

    VictoriaMetrics supports Prometheus-compatible workflows with both single-node and clustered deployments, making smaller setups possible, with enterprise capabilities licensed separately.

  • Grafana Mimir

    Store Prometheus-compatible metrics over long periods at distributed scale.

    Grafana Mimir stores Prometheus-compatible metrics long term with multi-tenancy and Grafana integration under AGPL-3.0, though distributed operation needs substantial configuration.

  • InfluxDB

    Store time-stamped measurements for monitoring and real-time applications.

    InfluxDB is a time-series database with self-hosted and managed editions, though features and compatibility differ significantly between its product generations.

  • GreptimeDB

    Store observability data in a database queried through SQL and PromQL.

    GreptimeDB stores time-series telemetry queried through SQL and PromQL, with object-storage-oriented deployments under Apache-2.0 and a freemium model.

  • TimescaleDB

    PostgreSQL extension that turns Postgres into a scalable time-series database.

    TimescaleDB extends PostgreSQL for time-series workloads, keeping Postgres tooling, while advanced clustering and cloud features sit behind the paid offering.

  • QuestDB

    Query time-series data with a database focused on SQL and high-rate ingestion.

    QuestDB focuses on time-oriented SQL and high-rate ingestion rather than Prometheus compatibility, with managed and enterprise capabilities under separate terms.

Similar software

Related functionality, not a direct replacement.