Learn how Apache Druid and TimescaleDb 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
Self-hosted
Repository

Both Apache Druid and TimescaleDb 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.
TimescaleDb leads in popularity with 23,465 stars vs 14,051 stars for Apache Druid. The 67% higher star count indicates stronger community adoption. In terms of developer contributions, Apache Druid has 3,802 forks, indicating strong developer engagement.
TimescaleDb is growing faster, adding 219 stars in the last 30 days (+0.9%) against adding 10 stars for Apache Druid (+0.1%). TimescaleDb is both larger and pulling further ahead.
Both projects show recent activity, with Apache Druid last updated 1 day ago and TimescaleDb 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 TimescaleDb leverages C, Objective-C, Perl.
Apache Druid has been in development longer, starting 14 years ago, compared to TimescaleDb which began 10 years ago. This 4.4-year head start suggests Apache Druid may have more mature features and established processes.
Apache Druid is licensed under Apache-2.0, while TimescaleDb's license terms are not publicly specified.
Both tools serve similar use cases in Time Series Databases. However, they also have distinct specializations: TimescaleDb extends into Relational Databases (SQL).
Both Apache Druid and TimescaleDb offer self-hosting capabilities, giving you full control over your data and infrastructure.