Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

LindormTSDB review

#3 of 36 in Time-Series Databases

A broad compatibility layer for teams managing scalable telemetry and metrics workloads.

9.0/10Editor score
LindormTSDB9.0 Visit Alibaba Cloud

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

LindormTSDB is Alibaba Cloud’s managed time-series database engine for measurement, device, IoT, telemetry, and monitoring data. It is designed for teams that need multiple ingestion and query paths rather than a single database interface. SQL access is available through JDBC, the HTTP SQL API, and the Lindorm CLI, while ingestion supports SQL INSERT, InfluxDB line protocol, OpenTSDB APIs, and Prometheus remote write. PromQL querying is also supported, giving monitoring teams a familiar route into stored metrics.

Its ecosystem fit is a central strength. Grafana, Prometheus, InfluxDB, OpenTSDB, and JDBC are documented integrations, so teams can connect existing observability and analytics workflows across compatible protocols. The database also supports compression, aggregation, spatial aggregation, interpolation, downsampling, TTL-based retention, and hot/cold data tiering. These capabilities make it suitable for workloads where storage duration, query shape, and data temperature change over time. A distributed, decoupled storage-and-compute architecture provides horizontal scaling for growing workloads.

Lindorm ML adds in-database forecasting and anomaly detection, which can keep time-series analysis close to the stored data instead of requiring a separate processing path. That combination makes LindormTSDB a strong fit for managed cloud deployments with varied telemetry sources and a need for operational analytics. It is less suitable for teams seeking a narrow, self-managed database deployment or a minimal setup with only one query and ingestion model. Buyers should also account for cloud billing that varies by region and configuration when evaluating fit.

LindormTSDB pros and cons

  • Where it wins
    • Supports SQL, PromQL, InfluxDB, OpenTSDB, and Prometheus workflows
    • Combines compression, downsampling, retention, and hot/cold tiering
    • Includes in-database forecasting and anomaly detection through Lindorm ML
  • Where it doesn't
    • Cloud deployment may not suit teams requiring self-managed infrastructure
    • Its broad interface set may add platform decisions for smaller workloads
    • Billing varies by region and configuration

LindormTSDB fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update