Skip to content

GreptimeDB vs. M3DB

M3DB release cadence has slowed significantly — the last formal release was v1.5.0 in April 2022. Operating it means juggling M3 Coordinator, M3 Aggregator, M3 Query, and etcd. Metrics only, no logs or traces.

M3DB comparison at a glance.
See what changes operationally at scale.

M3DB was developed by Uber for large-scale metrics storage. Active development has slowed significantly. It features a multi-component architecture — M3 Coordinator, M3 Query, M3 Aggregator, and etcd — that is complex to operate. Metrics only; no native support for logs, traces, or OpenTelemetry.

CHALLENGER

M3DB

Release cadence slowed significantly · complex multi-component ops (Coordinator, Aggregator, etcd) · metrics only

VS

GREPTIMEDB

GreptimeDB

Actively maintained, simpler architecture, unified observability

Feature comparison
Feature/AspectGreptimeDBM3DB
Data ModelMetrics, Logs & Traces in one databaseDistributed Time-Series Database
Value ModelMulti-Value (supports complex data structures)Single-Value (Prometheus metrics)
Multi-model SupportMetrics, Logs & Traces in one databaseMetrics only (requires separate systems for logs/traces)
Query LanguagesSQL & PromQL (dual interface)PromQL (100% compatibility) & M3QL
Ingestion ProtocolsSQL
gRPC
InfluxDB Line Protocol
Prometheus Remote Storage
OpenTelemetry
Loki Push API
Elasticsearch Bulk API
HTTP API
Prometheus Remote Write
M3 Coordinator API
Carbon (Graphite)
Data RetentionFlexible TTL policies with tiered storageConfigurable retention with automatic expiration
Continuous AggregationBuilt-in SQL aggregation, Pipeline ETL engine & Flow streaming computationM3 Aggregator with stream-based downsampling
Deployment ComplexitySingle system deploymentMulti-component deployment (coordinator, query, aggregator)
Use CasesUnified observability, real-time analytics, IoT monitoring, edge computingLarge-scale Prometheus monitoring, metrics aggregation
ArchitectureCloud-native distributed with compute-storage disaggregationMulti-component architecture (M3DB + M3 Coordinator + M3 Query + M3 Aggregator)
Storage FormatApache Parquet (columnar, compressed)M3TSZ compression (optimized Gorilla TSZ)
Storage ScalabilityObject storage integration with unlimited capacityDistributed storage with automatic sharding
High AvailabilityNative clustering with automatic failoverMulti-region deployment with quorum-based consistency
LicenseApache 2.0Apache 2.0
Written LanguageRust (memory safety, performance)Go (ecosystem compatibility)
Deployment OptionsSingle-node, cluster, Kubernetes-native, edge-to-cloud with unified APIMulti-component deployment with etcd coordination
Operational ComplexitySingle unified system with simplified Kubernetes operationsComplex multi-component operations

Stay in the loop

Join our community