Learn how Apache Druid and InfluxDB 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
11 hours agoRepository age
14 yearsVersion
38.0.0License
Apache-2.0Self-hosted
YesRepository
apache/druid
Last 30 days
Last commit
1 day agoRepository age
13 yearsVersion
v3.12.2License
Apache-2.0Self-hosted
YesRepository
influxdata/influxdb
Both Apache Druid and InfluxDB have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
InfluxDB leads in popularity with 31,803 stars vs 14,098 stars for Apache Druid. The 126% higher star count indicates stronger community adoption. In terms of developer contributions, InfluxDB has 3,825 forks, indicating strong developer engagement.
Apache Druid and InfluxDB are moving at much the same rate, adding 40 stars and adding 44 stars respectively over the last 30 days (+0.3% vs +0.1%). Neither is pulling away from the other on momentum alone.
Both projects show recent activity, with Apache Druid last updated 11 hours ago and InfluxDB 1 day ago.
Both tools share common technology foundations, being built with Bash, Python. However, they differ in their additional technology choices: Apache Druid uses JavaScript, CSS, Typescript, JSX, SCSS, Java while InfluxDB leverages Rust.
Both projects started around the same time, with Apache Druid beginning 14 years ago and InfluxDB 13 years ago.
Both projects use the Apache-2.0 license, providing identical terms for usage and distribution.
Both tools serve similar use cases in Time Series Databases.
Both Apache Druid and InfluxDB offer self-hosting capabilities, giving you full control over your data and infrastructure.