Skip to content

GreptimeDB vs. InfluxDB

InfluxDB's version history is fragmented — v1, v2, and v3 differ in storage format, query language, and licensing. In TSBS benchmark tests, GreptimeDB writes 2x faster and queries 2-11x faster. It handles 1B+ rows that InfluxDB OSS can't, and offers one consistent API from edge to cloud.

Line protocol wrote it.
TSM compacted it.

InfluxDB is a time-series database developed by InfluxData for monitoring, IoT, and analytics. It evolved through multiple versions: v1/v2 use the TSM storage engine with InfluxQL and Flux query languages, while v3 adopts Apache Parquet and Arrow. v3 Core is released under MIT/Apache 2.0, but v2.x remains under BSL 1.1. The version fragmentation — different storage formats, query languages, and licensing across major versions — is a key consideration for adopters. Click here to read the full performance comparison report between GreptimeDB and InfluxDB.

CHALLENGER

InfluxDB

Version-fragmented · TSM (v1/v2), Parquet (v3) · Flux deprecated in v3

VS

GREPTIMEDB

GreptimeDB

Apache 2.0 · open Parquet storage · InfluxDB Line Protocol compatible

Feature comparison
Feature/AspectGreptimeDBInfluxDB
Data ModelMetrics, Logs & Traces in one databaseTime-Series Database
Value ModelMulti-Value (supports complex data structures)Multi-Value (tags and fields)
Multi-model SupportMetrics, Logs & Traces in one databaseMetrics only (requires separate systems for logs/traces)
Ingestion ProtocolsSQL
gRPC
InfluxDB Line Protocol
Prometheus Remote Storage
OpenTelemetry
Loki Push API
Elasticsearch Bulk API
HTTP API
InfluxDB Line Protocol
HTTP API
Telegraf plugins
Query LanguagesSQL & PromQL (dual interface)InfluxQL & Flux (v1/v2)
SQL & InfluxQL (v3)
Data RetentionFlexible TTL policies with tiered storageRetention policies with automatic deletion
Continuous AggregationBuilt-in SQL aggregation, Pipeline ETL engine & Flow streaming computationContinuous queries (v1/v2)
Tasks and checks (v3)
Use CasesUnified observability, real-time analytics, IoT monitoring, edge computingIoT monitoring, DevOps metrics, application monitoring
ArchitectureCloud-native distributed with compute-storage disaggregationSingle binary (v1/v2)
Cloud-native microservices (v3)
Storage FormatApache Parquet (columnar, compressed)TSM engine (v1/v2)
Apache Parquet (v3)
Storage ScalabilityObject storage integration with unlimited capacityLocal storage (v1/v2)
Object storage support (v3)
High AvailabilityNative clustering with automatic failoverEnterprise clustering (v1/v2)
Native HA (v3)
LicenseApache 2.0MIT/Apache 2.0 (v3 Core)
BSL 1.1 (v2.x)
Commercial (Enterprise/Cloud)
Deployment OptionsSingle-node, cluster, Kubernetes-native, edge-to-cloud with unified APISingle binary, containerized, cloud-managed
Version CompatibilityConsistent API from edge to cloud with unified control planeBreaking changes between major versions
Written LanguageRust (memory safety, performance)Go (v1/v2)
Rust (v3)

Stay in the loop

Join our community