From f3c8ef70115eabd196906e9655e2f5220b98c4a5 Mon Sep 17 00:00:00 2001 From: dennis zhuang Date: Fri, 27 Feb 2026 16:28:19 +0800 Subject: [PATCH] docs: update project status and description (#7731) * docs: update readme Signed-off-by: Dennis Zhuang * Update README.md Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> Signed-off-by: Dennis Zhuang * Update README.md Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> Signed-off-by: Dennis Zhuang * Update README.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: Dennis Zhuang * Update README.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: Dennis Zhuang * fix: html Signed-off-by: Dennis Zhuang * chore: update status Signed-off-by: Dennis Zhuang --------- Signed-off-by: Dennis Zhuang Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- README.md | 68 +++++++++++++++++++++++++++---------------------------- 1 file changed, 34 insertions(+), 34 deletions(-) diff --git a/README.md b/README.md index 6c83582a24..73141dcb05 100644 --- a/README.md +++ b/README.md @@ -6,16 +6,17 @@

-

Real-Time & Cloud-Native Observability Database
for metrics, logs, and traces

+

One database for metrics, logs, and traces
+replacing Prometheus, Loki, and Elasticsearch

-> Delivers sub-second querying at PB scale and exceptional cost efficiency from edge to cloud. +> The unified OpenTelemetry backend — with SQL + PromQL on object storage.

User Guide | API Docs | Roadmap 2025 -

+ Version @@ -51,7 +52,7 @@ - [Introduction](#introduction) - [⭐ Key Features](#features) -- [Quick Comparison](#quick-comparison) +- [How GreptimeDB Compares](#how-greptimedb-compares) - [Architecture](#architecture) - [Try GreptimeDB](#try-greptimedb) - [Getting Started](#getting-started) @@ -66,42 +67,40 @@ ## Introduction -**GreptimeDB** is an open-source, cloud-native database that unifies metrics, logs, and traces, enabling real-time observability at any scale — across edge, cloud, and hybrid environments. +**GreptimeDB** is an open-source observability database that handles metrics, logs, and traces in one engine. Use it as the single OpenTelemetry backend — replacing Prometheus, Loki, and Elasticsearch with one database built on object storage. Query with SQL and PromQL, scale without pain, cut costs up to 50x. ## Features | Feature | Description | | --------- | ----------- | -| [All-in-One Observability](https://docs.greptime.com/user-guide/concepts/why-greptimedb) | OpenTelemetry-native platform unifying metrics, logs, and traces. Query via [SQL](https://docs.greptime.com/user-guide/query-data/sql), [PromQL](https://docs.greptime.com/user-guide/query-data/promql), and [Flow](https://docs.greptime.com/user-guide/flow-computation/overview). | -| [High Performance](https://docs.greptime.com/user-guide/manage-data/data-index) | Written in Rust with [rich indexing](https://docs.greptime.com/user-guide/manage-data/data-index) (inverted, fulltext, skipping, vector), delivering sub-second responses at PB scale. | -| [Cost Efficiency](https://docs.greptime.com/user-guide/concepts/architecture) | 50x lower operational and storage costs with compute-storage separation and native object storage (S3, Azure Blob, etc.). | -| [Cloud-Native & Scalable](https://docs.greptime.com/user-guide/deployments-administration/deploy-on-kubernetes/greptimedb-operator-management) | Purpose-built for [Kubernetes](https://docs.greptime.com/user-guide/deployments-administration/deploy-on-kubernetes/greptimedb-operator-management) with unlimited cross-cloud scaling, handling hundreds of thousands of concurrent requests. | -| [Developer-Friendly](https://docs.greptime.com/user-guide/protocols/overview) | SQL/PromQL interfaces, built-in web dashboard, REST API, MySQL/PostgreSQL protocol compatibility, and native [OpenTelemetry](https://docs.greptime.com/user-guide/ingest-data/for-observability/opentelemetry/) support. | -| [Flexible Deployment](https://docs.greptime.com/user-guide/deployments-administration/overview) | Deploy anywhere from ARM-based edge devices (including [Android](https://docs.greptime.com/user-guide/deployments-administration/run-on-android)) to cloud, with unified APIs and efficient data sync. | +| Drop-in replacement | [PromQL](https://docs.greptime.com/user-guide/query-data/promql/), [Prometheus remote write](https://docs.greptime.com/user-guide/ingest-data/for-observability/prometheus/), [Jaeger](https://docs.greptime.com/user-guide/query-data/jaeger/), and [OpenTelemetry](https://docs.greptime.com/user-guide/ingest-data/for-observability/opentelemetry/) native. Use as your single backend for all three signals, or migrate one at a time.| +| 50x lower cost | Object storage (S3, GCS, Azure Blob etc.) as [primary storage](https://docs.greptime.com/user-guide/deployments-administration/configuration/#storage-options). Compute-storage separation scales without pain.| +| SQL + PromQL | Monitor with [PromQL](https://docs.greptime.com/user-guide/query-data/promql), analyze with [SQL](https://docs.greptime.com/user-guide/query-data/sql). One database replaces Prometheus + your data warehouse.| +| Sub-second at PB-EB scale | Columnar engine with [fulltext, inverted, and skipping indexes](https://docs.greptime.com/user-guide/manage-data/data-index). Written in Rust.| ✅ **Perfect for:** - - Unified observability stack replacing Prometheus + Loki + Tempo - - Large-scale metrics with high cardinality (millions to billions of time series) - - Large-scale observability platform requiring cost efficiency and scalability - - IoT and edge computing with resource and bandwidth constraints + * Replacing Prometheus + Loki + Elasticsearch with one database + * Scaling past Prometheus — high cardinality, long-term storage, no Thanos/Mimir overhead + * Cutting observability costs with object storage (up to 50x savings on traces, 30% on logs) + * Edge-to-cloud observability with unified APIs on resource-constrained devices Learn more in [Why GreptimeDB](https://docs.greptime.com/user-guide/concepts/why-greptimedb) and [Observability 2.0 and the Database for It](https://greptime.com/blogs/2025-04-25-greptimedb-observability2-new-database). -## Quick Comparison +## How GreptimeDB Compares -| Feature | GreptimeDB | Traditional TSDB | Log Stores | -|----------------------------------|-----------------------|--------------------|-----------------| -| Data Types | Metrics, Logs, Traces | Metrics only | Logs only | -| Query Language | SQL, PromQL | Custom/PromQL | Custom/DSL | -| Deployment | Edge + Cloud | Cloud/On-prem | Mostly central | -| Indexing & Performance | PB-Scale, Sub-second | Varies | Varies | -| Integration | REST API, SQL, Common protocols | Varies | Varies | +| Feature | GreptimeDB | Prometheus / Thanos / Mimir | Grafana Loki | Elasticsearch | +|---|---|---|---|---| +| Data types | Metrics, logs, traces | Metrics only | Logs only | Logs, traces | +| Query language | SQL + PromQL | PromQL | LogQL | Query DSL | +| Storage | Native object storage (S3, etc.) | Local disk + object storage (Thanos/Mimir) | Object storage (chunks) | Local disk | +| Scaling | Compute-storage separation, stateless nodes | Federation / Thanos / Mimir — multi-component, ops heavy | Stateless + object storage | Shard-based, ops heavy | +| Cost efficiency | Up to 50x lower storage | High at scale | Moderate | High (inverted index overhead) | +| OpenTelemetry | Native (metrics + logs + traces) | Partial (metrics only) | Partial (logs only) | Via instrumentation | -**Performance:** -* [GreptimeDB tops JSONBench's billion-record cold run test!](https://greptime.com/blogs/2025-03-18-jsonbench-greptimedb-performance) +**Benchmarks:** +* [GreptimeDB tops JSONBench's billion-record cold run test](https://greptime.com/blogs/2025-03-18-jsonbench-greptimedb-performance) * [TSBS Benchmark](https://github.com/GreptimeTeam/greptimedb/tree/main/docs/benchmarks/tsbs) - -Read [more benchmark reports](https://docs.greptime.com/user-guide/concepts/features-that-you-concern#how-is-greptimedbs-performance-compared-to-other-solutions). +* [More benchmark reports](https://docs.greptime.com/user-guide/concepts/features-that-you-concern#how-is-greptimedbs-performance-compared-to-other-solutions) ## Architecture @@ -171,21 +170,22 @@ cargo run -- standalone start ## Project Status -> **Status:** Beta — marching toward v1.0 GA! -> **GA (v1.0):** January 10, 2026 +> **Status:** RC — marching toward v1.0 GA! +> **GA (v1.0):** March 2026 -- Deployed in production by open-source projects and commercial users -- Stable, actively maintained, with regular releases ([version info](https://docs.greptime.com/nightly/reference/about-greptimedb-version)) -- Suitable for evaluation and pilot deployments +- Deployed in production handling billions of data points daily +- Stable APIs, actively maintained, with regular releases ([version info](https://docs.greptime.com/nightly/reference/about-greptimedb-version)) GreptimeDB v1.0 represents a major milestone toward maturity — marking stable APIs, production readiness, and proven performance. -**Roadmap:** Beta1 (Nov 10) → Beta2 (Nov 24) → RC1 (Dec 8) → GA (Jan 10, 2026), please read [v1.0 highlights and release plan](https://greptime.com/blogs/2025-11-05-greptimedb-v1-highlights) for details. +**Roadmap:** [v1.0 highlights and release plan](https://greptime.com/blogs/2025-11-05-greptimedb-v1-highlights) and [2026 roadmap](https://greptime.com/blogs/2026-02-11-greptimedb-roadmap-2026). For production use, we recommend using the latest stable release. -[![Star History Chart](https://api.star-history.com/svg?repos=GreptimeTeam/GreptimeDB&type=Date)](https://www.star-history.com/#GreptimeTeam/GreptimeDB&Date) If you find this project useful, a ⭐ would mean a lot to us! + +[![Star History Chart](https://api.star-history.com/svg?repos=GreptimeTeam/GreptimeDB&type=Date)](https://www.star-history.com/#GreptimeTeam/GreptimeDB&Date) + Known Users ## Community