Learn how InfluxDB and TDengine differ in their key features, development activity, technology stack and community adoption, so you can decide which of these time series databases is best for you.
Last 30 days
Last commit
Repository age
Version
License
Self-hosted
Repository

Last 30 days
Last commit
Repository age
Version
License
Repository

InfluxDB appears to have several advantages over TDengine, particularly in maturity and features. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
Both tools have similar popularity levels, with InfluxDB having 31,714 stars and TDengine having 25,083 stars on GitHub. In terms of developer contributions, TDengine has 5,018 forks, indicating strong developer engagement.
InfluxDB and TDengine are moving at much the same rate, adding 59 stars and adding 83 stars respectively over the last 30 days (+0.2% vs +0.3%). Neither is pulling away from the other on momentum alone.
Both projects show recent activity, with InfluxDB last updated 5 days ago and TDengine 14 hours ago.
Both tools share common technology foundations, being built with Bash, Python, Rust. However, they differ in their additional technology choices: TDengine leverages JavaScript, CSS, Golang, C, Objective-C, PHP, Java, C++, MATLAB, C#, Lua, R, Ada.
InfluxDB has been in development longer, starting 13 years ago, compared to TDengine which began 7 years ago. This 5.9-year head start suggests InfluxDB may have more mature features and established processes.
The projects use different licenses: InfluxDB is licensed under Apache-2.0 while TDengine uses AGPL-3.0. Consider the licensing requirements when choosing for your project.
Both tools serve similar use cases in Time Series Databases.
InfluxDB provides self-hosting options for complete data control and customization, while TDengine may be primarily cloud-based or require different deployment approaches.