whichdb
vs

GridDB vs TDengine

GridDB: Toshiba's memory-first container database for IoT time series, with per-container ACID and SQL. TDengine: Industrial-IoT time-series database with a table-per-device model and built-in streaming and caching.

key differences

  • Transactions: GridDB offers limited ACID; TDengine offers none.
  • Only GridDB has transactions, in-memory.
  • Only TDengine has json, pub/sub, columnar storage, role-based access, streaming ingest.

choose griddb for

  • +Factory and plant sensor data
  • +Smart grid and energy monitoring
  • +Infrastructure monitoring for social systems
  • +IoT apps needing per-device transactional updates

best at · IoT, Time-series, OLTP

choose tdengine for

  • +Industrial IoT and SCADA historian replacement
  • +Connected-vehicle telemetry
  • +Smart meters and energy grids
  • +Edge-to-cloud sensor data aggregation

best at · IoT, Time-series, Streaming

GridDBToshiba's memory-first container database for IoT time series, with per-container ACID and SQL.
TDengineIndustrial-IoT time-series database with a table-per-device model and built-in streaming and caching.
overview
Primary model
Time-Series
Time-Series
Also supports
Key-Value, Relational
Relational
Type
Database engine
Database engine
Status
Active
Active
Developer
Toshiba Digital Solutions
TAOS Data
First release
2013
2019
Latest version
5.9.0 (Feb 18, 2026)
3.4.3.3 (Oct 19, 2026)
License
Open source (copyleft)GNU AGPL v3.0 (server); Apache-2.0 clients
Open source (copyleft)GNU AGPL v3.0 (open-source edition)
Free tier
✓
✓
popularity
WhichDB Score
10.7
17.4
Rank
#295
#192
GitHub stars
2.5K
25.2K
Stack Overflow questions
572
225
scale & guarantees
Comfortable data size
Large (≤ 1 PB)
Large (≤ 1 PB)
Horizontal scaling
Native
Native
Multi-region
None
None
ACID
Limited
None
Consistency
Tunable
Strong
Schema
Strict
Strict
Architecture
Distributed, In memory, Client server
Distributed, Single node, Client server
deployment
Self-hosted
✓
✓
Vendor-managed cloud
✓
✓
Serverless
—
—
Embedded
—
—
Edge
—
✓
Clouds
–
–
capabilities
Transactions
✓
—
Joins
✓
✓
Secondary indexes
✓
✓
Full-text search
—
—
Vector search
—
—
Geospatial
—
—
JSON
—
✓
Change data capture
—
—
Triggers
—
—
Stored procedures
—
—
Materialized views
—
—
TTL / expiry
✓
✓
Pub/Sub
—
✓
Columnar storage
—
✓
In-memory
✓
—
Durable persistence
✓
✓
Compression
✓
✓
Encryption at rest
—
—
Role-based access
—
✓
Time travel
—
—
Branching
—
—
Online schema changes
—
—
Streaming ingest
—
✓
Offline sync
—
—
Runs in WebAssembly
—
—
interfaces
Query languages
SQL, TQL
SQL
Client languages
Java, C, Python, Go, JavaScript
C, Java, Python, Go, Rust, JavaScript, C#
Best for
IoT, Time-series, OLTP
IoT, Time-series, Streaming, Real-time analytics
Add more to this comparisonNot sure either fits? Try smart match

GridDB vs TDengine: FAQ

What is the difference between GridDB and TDengine?

GridDB: Toshiba's memory-first container database for IoT time series, with per-container ACID and SQL. TDengine: Industrial-IoT time-series database with a table-per-device model and built-in streaming and caching. Transactions: GridDB offers limited ACID; TDengine offers none. Only GridDB has transactions, in-memory. Only TDengine has json, pub/sub, columnar storage, role-based access, streaming ingest.

When should I choose GridDB over TDengine?

Choose GridDB for factory and plant sensor data; smart grid and energy monitoring; and infrastructure monitoring for social systems. Choose TDengine for industrial IoT and SCADA historian replacement; connected-vehicle telemetry; and smart meters and energy grids.

Is GridDB or TDengine more popular?

TDengine ranks #192 on the WhichDB Score (17.4/100) and GridDB ranks #295 (10.7/100). Popularity is not fit: check the requirements that matter for your project.

Are GridDB and TDengine open source?

Yes. GridDB is open source. License: GNU AGPL v3.0 (server); Apache-2.0 clients. Yes. TDengine is open source. License: GNU AGPL v3.0 (open-source edition).